e2e test to validate correct url

validate http code of project's URL in ecosystem page

- `200` code can be soft-expected to be true
- `404` code can be expected to be false

Start by locating the ecosystem page and the existing end-to-end test setup in the repository. Trace how the project's URL is exposed there, then add coverage for the stated HTTP outcomes: 200 should be treated as true and 404 as false. Done means the end-to-end test reliably distinguishes those two responses.

Written by the indexing model from the issue text.