feat: Support page level full redirection

[FentPams]

Description

The aim is to run full-page experimentation and personalization use cases that fully redirect to the target URL instead of just replacing the content for a marketer.

The new properties are introduced:

Experiment Resolution | redirect
Audience Resolution   | redirect
Campaign Resolution   | redirect

When simulate the variant, rather than 'replace' the page, url is redirected by calling window.location.replace(url) API

How Has This Been Tested?

Test link:

• wknd page
• wknd doc

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.

[FentPams]

@ramboz Could you help review this? Please let me know where I could improve. Thank you :)

[ramboz]

A few minor fine-tuning comments, but otherwise all good 👍

[codecov]

Codecov Report

Attention: Patch coverage is 83.33333% with 5 lines in your changes missing coverage. Please review.

Please upload report for BASE (v2@942948d). Learn more about missing BASE report.

Files	Patch %	Lines
src/index.js	83.33%	4 Missing and 1 partial ⚠️

Additional details and impacted files

@@          Coverage Diff          @@
##             v2      #43   +/-   ##
=====================================
  Coverage      ?   92.89%           
=====================================
  Files         ?        1           
  Lines         ?      704           
  Branches      ?       12           
=====================================
  Hits          ?      654           
  Misses        ?       38           
  Partials      ?       12           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[FentPams]

@ramboz Could you help review this again? Thank you :)

I realized the test failures were caused by the fireRUM function. Initially, I defined all configurations upfront—experiment, campaign, and audience—regardless of whether runExperiment, runCampaign, or serveAudience was calling it. To fix it, I refactored it to create configurations only when needed.

Also, I added this part into documentation 😀

And I figured out why my local npm test always fail all tests:

1. My local repo was somehow messed up. 😅
2. I have aem up when I run test, they are using the same port number...
   So, I re-clone the repo and never forget to stop the aem up before running test locally :) Now it works well.