feat: track external redirect estimates

[ramboz]

Provides an updated redirect facet that highlights the time lost in redirects and also separates internal vs. external ones.

Description

With https://github.com/adobe/helix-rum-enhancer/pull/516, we are introducing a more fine-grained redirect checkpoint for which the value will change from 1 (redirect count) to 1:150 or 2~237 (redirect count and redirect time)

The goal here is to update the redirect facts to:

• surface the time lost in those redirects
• allow slicing and dicing by internal vs external redirects in our analysis.

Motivation and Context

See discussion in https://cq-dev.slack.com/archives/C07198KKQ07/p1761333727781429

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [ ] I have signed the Adobe Open Source CLA.
• [ ] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [ ] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [ ] All new and existing tests passed.

[aem-code-sync[bot]]

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 PSI checks
• [ ] Re-sync branch

Commits

• da5dc63 :white_check_mark: (latest)
• 76b4cae :white_check_mark: