Annotates archive explorer tests as Selenium-only

[davelopez]

Pending Playwright support, not sure yet what is needed to make them compatible 🤔

This should avoid these CI failures for now:

FAILED lib/galaxy_test/selenium/test_archive_explorer.py::TestArchiveExplorer::test_search_filters_files - playwright._impl._errors.TimeoutError: ElementHandle.click: Timeout 30000ms exceeded.
Call log:
  - attempting click action
    2 × waiting for element to be visible, enabled and stable
      - element is not visible
    - retrying click action
    - waiting 20ms
    2 × waiting for element to be visible, enabled and stable
      - element is not visible
    - retrying click action
      - waiting 100ms
    56 × waiting for element to be visible, enabled and stable
       - element is not visible
     - retrying click action
       - waiting 500ms
FAILED lib/galaxy_test/selenium/test_archive_explorer.py::TestArchiveExplorer::test_select_all_functionality - playwright._impl._errors.TimeoutError: ElementHandle.click: Timeout 30000ms exceeded.
Call log:
  - attempting click action
    2 × waiting for element to be visible, enabled and stable
      - element is not visible
    - retrying click action
    - waiting 20ms
    2 × waiting for element to be visible, enabled and stable
      - element is not visible
    - retrying click action
      - waiting 100ms
    55 × waiting for element to be visible, enabled and stable
       - element is not visible
     - retrying click action
       - waiting 500ms
    - waiting for element to be visible, enabled and stable

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[jmchilton]

I think this is the right approach for now. I'll try to work through the compat .differences in existing tests some time but I think these decorators are totally fine for the foreseeable future - I think it is more important to get tests written than to have them working within one framework or the other.