ci: expose nginx port via warden override for e2e access

[digitalrisedorset]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/mage-os/github-actions/blob/main/CONTRIBUTING.md#commit
• Tests for the changes have been added (not applicable)
• Docs have been added / updated (not applicable)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

The Warden environment starts successfully in CI, but no HTTP service is exposed to the GitHub Actions runner.

As a result, e2e tests cannot reach the application (no accessible localhost endpoint).

What is the new behavior?

Adds a Warden override (.warden/warden-env.yml) to expose the web service on localhost:8080.

This provides a reachable HTTP endpoint for e2e tests in CI.

Does this PR introduce a breaking change?

• Yes
• No

Other information

This change assumes nginx is the entrypoint exposed by Warden.

If Warden routes traffic via Traefik in CI, exposing Traefik instead may be more appropriate. This PR establishes a baseline to validate HTTP reachability.

[damienwebdev]

@rhoerr @digitalrisedorset I don't plan to use warden to run tests in CI. I have no familiarity with it and it's seems like far too much overkill for me for what we're trying to accomplish. I'm unassigning myself from review for this as such.