[topunix]

Bug 1851435

The Selenium and webservice suites were not reachable through
docker/run-tests-in-docker.sh. The script hardcoded TEST_NAME to
test_bmo or test_sanity, so the only way to run qa/t was a direct
docker compose run against the test stack. Documenting a single entry
point meant making one exist, so this adds the two missing options
alongside the docs.

docker/run-tests-in-docker.sh

• Adds menu options 7 (selenium) and 8 (webservices), mapping to the
  existing cmd_test_selenium and cmd_test_webservices in
  scripts/entrypoint.pl.
• Both use docker-compose.test-mysql.yml, which already provides the
  selenium/standalone-firefox service the QA suites need.
• Both set DEFAULT_TEST_ARGS=(), because those two entrypoint commands
  take no file arguments and would otherwise inherit the t/bmo/*.t
  default.
• Updates the usage line.

No change to the existing options and no change to ci.yml. The browser
suite takes roughly 30 minutes, which is too slow for a merge gate, so it
stays available through the container only.

docker/README.md

Adds a "Running the Test Suites" section covering the option table, the
Selenium service and its configuration, how the QA suites are driven
through scripts/entrypoint.pl, and two known failures: the account
creation tests that are being reworked by the login/email separation
work, and an intermittent assertion in
test_edit_products_properties.t.

Notes

• shellcheck -x is clean.
• The script is committed non-executable (100644), so the README examples
  use bash docker/run-tests-in-docker.sh. I can add the mode bit in a
  separate commit if you would rather it be directly invocable.
• Separately, generate_test_data.pl currently aborts during test data
  loading with a duplicate Priority value, which stops the QA suites
  before any test runs. I am still isolating whether that is local state
  or a regression, and will report it on its own bug rather than folding
  it in here.

[justdave]

Looks good, thanks!