Rewrite pyramid tests

[pwalczysko]

What this PR does

Rewrites pyramid tests in the OmeroPy suite contained inside pytest test/integration/clitest/test_pyramids.py .
As these tests are operating strictly on OMERO-pyramids (under /OMERO/Pixels) and not on pyramids which are part of the imported file, the strategy taken here had to be to skip the tests with clarification, see comment of @sbesson #6471 (comment)

This PR:

• Reverts the PR Fix test_pyramids.py little and big_endian #6464 which was merged already and which used polling tactics to force the tests passing
• Skips the pure pyramid tests using the @pytest.mark.skipif
• Adds comments to test classes explaining the character of the tested admin removepyramids cmd which is operating on OMERO pyramids only
• Renames the tests to test_omero_pyramids.py to make the situation obvious

Testing this PR

Check if the tests in the OmeroPy suite contained inside pytest test/integration/clitest/test_pyramids.py either pass or are skipped.

Related reading

Note this is related to #6470

[pwalczysko]

This needs a total rethink. The replacement of the single-plane-fake file import with an import of a fake file with pyramids included has grave consequences on the whole philosophy of this test suite, which is mainly testing the CLI command removepyramids https://github.com/ome/omero-py/blob/5d0974d097e25d98892b9b419528edf9256274b0/src/omero/util/cleanse.py#L383. This cmd is relying for its basic functioning on pyramid files being present under /OMERO/Pixels. Such omero-pyramids are not present when I import a fake file with pyramids included. My attempts up till now to fix the tests were nonsensical, as one cannot delete "undeletable" pyramids which are a part of the image file itself.

Atm, the only reasonable approach seems to be skipping the failing tests here.

cc @sbesson

[sbesson]

Agreed, this is an example of tests which specifically test and depend on OMERO pyramids. I think skipping them (conditionally to either the configuration or environment) is the best course of action.

An additional clarification idea would be to rename the tests e.g. as test_omero_pyramids and add some comments clarifying their scope.

[pwalczysko]

Agreed, this is an example of tests which specifically test and depend on OMERO pyramids. I think skipping them (conditionally to either the configuration or environment) is the best course of action.

An additional clarification idea would be to rename the tests e.g. as test_omero_pyramids and add some comments clarifying their scope.

Thank you @sbesson . Fixes pushed accordingly see the 4 commits above. Also edited the header of this PR to make the situation clear and adding the Include to confirm on Jenkins.

[pwalczysko]

The build https://merge-ci.openmicroscopy.org/jenkins/job/OMERO-test-integration/lastCompletedBuild/ is not having any failures from the tests in this PR, all pass or skipped as expected.