feat(workflows): add docker container testing workflow

[srmanda-cs]

What this PR does / why we need it:

Which issue(s) this PR closes:

• Closes #

Special notes for your reviewer:

Suggestions on how to test this:

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Is there a release notes update needed for this change?:

Additional documentation:

[Copilot]

Pull request overview

Adds a new GitHub Actions workflow intended to stand up the Docker-based dev stack and perform container-level validation on pushes and PRs targeting develop.

Changes:

• Introduces .github/workflows/container_testing_run.yml triggered on push/pull_request to develop (with docs-only path ignores).
• Builds/starts the docker-compose-dev.yml stack and waits for the Dataverse API readiness endpoint.
• Sets up Python and checks Chrome availability, then tears down containers and prunes Docker state.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The workflow stops the Docker daemon and deletes /var/lib/docker//var/lib/containerd, but it never starts Docker again. As a result, docker version (and later docker compose ...) will fail with "Cannot connect to the Docker daemon" on most runners. Start the Docker service again (and optionally wait until it’s active) before running any Docker commands, or remove the stop/wipe step if it’s not required.

[Copilot]

pip install -r tests/requirements.txt will fail because tests/requirements.txt does not exist in the repository. Either add this requirements file (and keep it in sync with the Python/Selenium tests), or update the workflow to install dependencies from the location the project actually uses (e.g., a pinned requirements file or pyproject.toml).

Suggested change

	pip install -r tests/requirements.txt
	if [ -f tests/requirements.txt ]; then
	echo "Installing test dependencies from tests/requirements.txt"
	pip install -r tests/requirements.txt
	elif [ -f requirements.txt ]; then
	echo "tests/requirements.txt not found; installing from root requirements.txt"
	pip install -r requirements.txt
	elif [ -f pyproject.toml ]; then
	echo "No requirements file found; installing project from pyproject.toml"
	pip install .
	else
	echo "Error: No dependency definition found (tests/requirements.txt, requirements.txt, or pyproject.toml)." >&2
	exit 1
	fi

[Copilot]

The job is named container-test and sets up Python/Selenium, but it never actually runs any tests after bringing the compose stack up (it only verifies Chrome and then tears everything down). Add an explicit test execution step (e.g., run the existing Python unittest suite, or whichever container/API checks this workflow is meant to validate) so the workflow provides real signal.

Suggested change

	- name: Run Selenium tests
	run: |
	set -euo pipefail
	python -m unittest discover -s tests -p "test_*.py"