[MILO][MEP] Update Manifest Type and Manifest Ordering v2

[vgoodric]

Redoing the PR. At some point file changes that weren't mine were being counted as my file updates.

Problem statement: The current order that MEP executes manifests is based on the source of the manifest. Instead, we need to use the manifest type to be sure that the manifests execute in a logical order.

Requirements:

• Separate Manifest Type "Test or Promo" into 2 separate items in the dropdown.
• Add a Manifest Execution Order, default value "normal", other values "first" and "last"
• Manifest order will first be determined the the manifest execution order field: first, normal then last.
• If there is more than one manifest of the same "execution order", the manifest type will break the tie. First Personalization, Promo then Test.

Note: previously, we would:

1. run cleanManifestList to remove duplicates
2. loop through the manifests
3. fire runPersonalization for each manifest
4. within runPersonalization we would fire getPersConfig to get manifest contents

Because we now need to know the contents to determine the order, we now:

1. loop through the manifests
2. fire getPersConfig on each manifest to get contents
3. fire cleanAndSortManifestList to merge duplicate manifest data and sort manifests
4. loop through the manifests in their new sorted order
5. fire runPersonalization for each manifest

Resolves: MWPW-142965

Test URLs:
2 manifests (1 pzn and 1 test from Target):
Before: https://mepmoreactions--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/two-manifests-one-from-target
After: https://mepmanifestorder2--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/two-manifests-one-from-target

A bunch of additional Test URL's to test different use cases (these are all captured by unit tests as well):
3 manifests with one of each manifest type in the "wrong" execution order:
Before: https://mepmoreactions--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/three-manifest-types-all-normal
After: https://mepmanifestorder2--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/three-manifest-types-all-normal

Same as above but one manifest using first:
Before: https://mepmoreactions--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/three-manifest-types-one-first
After: https://mepmanifestorder2--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/three-manifest-types-one-first

Same as above but one manifest using last:
Before: https://mepmoreactions--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/three-manifest-types-one-last
After: https://mepmanifestorder2--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/three-manifest-types-one-last

Same as above but old "Test or Promo" type being used:
Before: https://mepmoreactions--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/three-manifest-types-one-test-or-promo
After: https://mepmanifestorder2--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/three-manifest-types-one-test-or-promo

Same as above but one has no info tab:
Before: https://mepmoreactions--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/three-manifest-types-one-no-type
After: https://mepmanifestorder2--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/three-manifest-types-one-no-type

Improved merge also solves: https://jira.corp.adobe.com/browse/MWPW-143068
Before: https://mepmoreactions--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/outdated-manifest
After: https://mepmanifestorder2--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/outdated-manifest

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

Commits

• ab71b35 ✅ (latest)
• 330b0ce ✅
• 79267af ✅
• 1d64206 ✅
• 9a0cea9 ✅
• 1575a7f ✅
• 2664595 ✅
• ca185e5 ✅
• d96926b ✅
• 6294c18 ✅
• a0a9878 ✅
• 464d030 ✅

[aem-code-sync]

Page	Scores	Audits	Google
/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/outdated-manifest
/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/three-manifest-types-all-no rmal
/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/three-manifest-types-one-fi rst
/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/three-manifest-types-one-la st
/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/three-manifest-types-one-no -type
/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/three-manifest-types-one-te st-or-promo
/drafts/vgoodrich/fragments/2024/q1/mepmanifestorder/two-manifests-one-from-targ et

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.27%. Comparing base (ecdf107) to head (ab71b35).

Additional details and impacted files

@@                Coverage Diff                 @@
##           mepmoreactions    #1980      +/-   ##
==================================================
+ Coverage           96.24%   96.27%   +0.03%     
==================================================
  Files                 165      165              
  Lines               42381    42404      +23     
==================================================
+ Hits                40790    40826      +36     
+ Misses               1591     1578      -13     

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