Support multiple activations page metrics

[HarveyPeachey]

Resolves N/A

Summary

Changes OptimizelyPageMetrics to check all experiments have been activated on the page, before rendering.

This will force devs to keep the list up to date, and make it more accurate for when page views will be sent.

Code changes

• Uses every instead of some for checking activated experiments

Testing

1. List the steps required to test this PR.

Useful Links

• Coding Standards
• Repository use guidelines
• Add Links to useful resources related to this PR if applicable.

[Copilot]

Pull request overview

Tightens the gating in OptimizelyPageMetrics so page metric trackers only render once all experiments configured for the current page type have notified an activation decision, replacing the previous "any one activated" check. This forces the experimentsForPageMetrics list to be kept accurate and makes page view tracking emission timing more deterministic.

Changes:

• Switch from some to every when checking activated experiments against the page type configuration.
• Update existing tests to notify decisions for both configured experiments so they continue to render trackers.
• Add a new test asserting trackers are not rendered when only one of multiple configured experiments has been activated.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
src/app/components/OptimizelyPageMetrics/index.tsx	Require every configured experiment for the page type to be activated before rendering trackers.
src/app/components/OptimizelyPageMetrics/index.test.tsx	Adjust existing tests to notify both experiments and add a negative test for partial activation.