DACCESS-737: Fix Jenkins test permission issues

[JeremyDuncan]

Jira Ticket: https://culibrary.atlassian.net/browse/DACCESS-737

Description

Updates the Jenkins CI pipeline and Docker test image to run test containers as the Jenkins user instead of root, ensuring coverage output files are written with Jenkins-owned permissions.

File	Change
docker-compose-test.yaml & docker-compose-test-interactive.yaml	Passes DOCKER_UID/DOCKER_GID as the container user, and sets HOME=/tmp so tools like Bundler and Selenium Manager have a writable home directory when running as a non-root UID
cucumber-features.sh / rspec.sh	Exports DOCKER_UID/DOCKER_GID from the Jenkins shell and pre-creates the coverage directory with mkdir -p so it is owned by Jenkins before the container writes to it
Dockerfile (test stage)	Adds chmod -R a+rwX on /root, APP_PATH, and BUNDLE_PATH so the non-root Jenkins user can write to Chrome user-data directories, app temp files, and the gem bundle
Jenkinsfile	Removes redundant mkdir -p coverage / chmod / dummy-file lines from the Publish Coverage stage that were creating a root-owned coverage/ directory at the wrong path in the workspace

Reason for Changes

Jenkins was failing to clean its workspace between builds because SimpleCov coverage output files (.resultset.json, index.html, rcov/, etc.) were being written as root inside the bind-mounted coverage directory. Since Jenkins runs as a non-root user it could not delete those files during workspace cleanup, causing CompositeIOException: Unable to delete errors on every subsequent build.

---

Before:

After:

[JeremyDuncan]

I have this branch deployed to Integration as well.