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

[BilalQamar95]

Description
Major version upgrades, Updating frontend-build to v14 & frontend-platform to v8 along with respective edx packages

[justinhynes]

Hi @BilalQamar95,

This is a draft PR that doesn't look like it has moved much lately. Is this still planned or required work? Can this be closed?

[BilalQamar95]

Hi @BilalQamar95,

This is a draft PR that doesn't look like it has moved much lately. Is this still planned or required work? Can this be closed?

@justinhynes This is still planned from our side, some other PRs of ours are awaiting review, once they are merged dependency issues in this will be cleared out.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.73%. Comparing base (4445fe3) to head (55cad26).
Report is 28 commits behind head on master.

❗ Current head 55cad26 differs from pull request most recent head fa00386

Please upload reports for the commit fa00386 to get more accurate results.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #246      +/-   ##
==========================================
- Coverage   70.87%   70.73%   -0.15%     
==========================================
  Files          28       28              
  Lines         412      410       -2     
  Branches       89       87       -2     
==========================================
- Hits          292      290       -2     
  Misses        119      119              
  Partials        1        1              

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

[justinhynes]

HI @BilalQamar95 -- it looks like you marked this as ready, but there are a couple of conflicts that need to be resolved in the package.json and package-lock.json files. Any chance you can fix this up and then I can get this on my radar this week while I'm on call?

[BilalQamar95]

HI @BilalQamar95 -- it looks like you marked this as ready, but there are a couple of conflicts that need to be resolved in the package.json and package-lock.json files. Any chance you can fix this up and then I can get this on my radar this week while I'm on call?

@justinhynes I have resolved the conflicts