[fiesta] Warn on duplicate fragment references within a page

[shkhan91]

• When the same fragment path is referenced more than once on a single page, no signal is given to the content author or developer
• This can silently produce unexpected rendering behavior and is hard to diagnose
• A single, deduplicated console warning per duplicated path is required; loading behavior must remain unchanged

Resolves:

Test URLs:

• Before: https://stage--milo--adobecom.aem.page/?martech=off
• After: https://fiesta-feat-warn-on-duplicate-fragment-references-26d824--milo--shkhan91.aem.page/?martech=off

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

• Re-run all PSI checks
• Re-run failed PSI checks
• Re-sync branch

Commits

• 2d2635c ❌ (latest)

[aem-code-sync]

	Page	Scores	Audits	Google
📱	/?martech=off		Lighthouse returned error: FAILED_DOCUMENT_REQUEST. Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Details: net::ERR_CONNECTION_FAILED)
🖥️	/?martech=off		Lighthouse returned error: FAILED_DOCUMENT_REQUEST. Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Details: net::ERR_CONNECTION_FAILED)