fix: Fix file workflow test for container environments

[pkoprda]

• Card ID: CCT-994

The test for updating info in the archive was failing in containers, which are not in charge of their own hostnames. This commit resolves the test failures by simulating hostname updates through archive file modification.

---

This pull request should be also backported to following maintenance branches:

• el9 (all of RHEL 9)
• el8 (all of RHEL 8)

[m-horky]

I'm not sure it is a good idea to have a test do wildly different things when running on a host/container. Unless we test it elsewhere already, I'd drop the code changing hostnames and only go with the modified archive.

[pkoprda]

Unless we test it elsewhere already, I'd drop the code changing hostnames and only go with the modified archive.

I kept the original test as was before (I just dropped unnecessary sleep from the test, see the reason in PR description) and I added a new test test_file_workflow_archive_modification_and_upload which is testing modification of the archive and then uploading to Ingress. However, there are already some tests for that in test_upload.py, so I am not sure if this new test is necessary.

[m-horky]

If the whole task of this new test is to verify that modified archive gets reflected in Inventory, it 1/ feels like a test Inventory should have, not insights-client, and 2/ we already do that in test_tags.py, just for a different files.

Also, this patch now doesn't address the underlying problem of test_file_workflow_archive_update_host_infofailing because it is callinghostnamectl set-hostname` which does not work in containers.

[m-horky]

All things considered, LGTM. I'm not too happy insights-client does this functionality through the Core, and it might be better to test this through the Core collection, but since it also is a question of integration, we might as well do it.