Page Health scanner (a11y / GEO) resolves the wrong site on multisite instances

Problem Statement

The Page Health a11y and GEO reports in UVE scan the wrong site on multisite instances. Only the page path is sent to the scanner, so when multiple sites share a path (e.g. /index), dotCMS resolves the page against the request-derived site instead of the site open in the editor. Worse in headless/UVE, where the request host maps to no dotCMS site.

Steps to Reproduce

1. Two sites with a page at the same path (e.g. /index), with different content.
2. Open Site B's page in UVE.
3. Page Tools → Accessibility (or GEO).
4. Observed: report is for the wrong site.
5. Expected: report is for Site B's page.

Acceptance Criteria

• a11y and GEO reports scan the site currently open in the editor.
• Works for traditional and headless/UVE pages.
• Two sites sharing a path each produce their own report.

dotCMS Version

Latest main (introduced in #35212 / #35255).

Severity

Medium - Some functionality impacted

Links

NA