feat: updated frontend-build & frontend-platform major versions

[BilalQamar95]

Description

• Major version upgrades, Updated frontend-build to v14 & Updated frontend-platform to v8

Reference to respective MFEs with the build and platform major version upgrades to be released as minor versions instead of major

Merge checklist:

• Evaluate how your changes will impact existing consumers (e.g., frontend-app-learner-portal-enterprise, frontend-app-admin-portal, and frontend-app-enterprise-public-catalog). Will consumers safely be able to upgrade to this change without any breaking changes?
• Ensure your commit message follows the semantic-release conventional commit message format. If your changes include a breaking change, ensure your commit message is explicitly marked as a BREAKING CHANGE so the NPM package is released as such.
• Once CI is passing, verify the package versions that Lerna will increment to in the Github Action CI workflow logs.
  • Note: This may be found in the "Preview Updated Versions (dry run)" step in the Github Action CI workflow logs.

Post merge:

• Verify Lerna created a release commit (e.g., chore(release): publish) that incremented versions in relevant package.json and CHANGELOG files, and created Git tags for those versions.
• Run the Publish from package.json Github Action workflow to publish these new package versions to NPM.
  • This may be triggered by clicking the "Run workflow" option for the master branch.
• Verify the new package versions were published to NPM (i.e., npm view <package_name> versions --json).
  • Note: There may be a slight delay between when the workflow finished and when NPM reports the package version as being published. If it doesn't appear right away in the above command, try again in a few minutes.

[adamstankiewicz]

[nit/sanity check] Will there be consuming MFEs still installing on frontend-platform v7 once these packages are upgraded in the consuming MFEs? If not, I'm wondering if frontend-platform v7 could be dropped in favor of only supporting v8 (though, doing so would require these packages to be released as a breaking change otherwise)?

[BilalQamar95]

Thank you touching on this. All MFEs will be moved to v8 once these packages are upgraded in the consuming MFEs. The initial proposal was indeed to transition all MFEs directly to frontend-platform v8, which would have necessitated a major version release due to breaking changes, which was opposed & there was a strong recommendation to maintain compatibility with frontend-platform v7 in order to avoid breaking change releases for the few MFEs having consumers. ([1], [2], [3]).

@abdullahwaheed has been a strong advocate of avoiding major version releases in this context & can elaborate on how the decision to prevent major version releases in this case, by maintaining frontend-platform v7 as a peer dependency, outweighs the benefits that might come from moving exclusively to v8 for a case where all MFEs are to be moved to v8 eventually.

As we continue with the implementation, as detailed in all related PRs, all MFEs will indeed be moved to frontend-platform v8 & frontend-build v14 as part of this coordinated upgrade process.

[abdullahwaheed]

@adamstankiewicz these new changes can work effectively with platform v7, so dropping its support and releasing a major change is not necessary. We will drop this support in future when we have some actual breaking change in this repo