Update to Address Security Vulnerabilities and Framework Enhancements

[dr-bizz]

Description

This PR addresses multiple security issues flagged by npm and Dependabot, involving major version upgrades and code adjustments.

Major Fixes

• Angular: Upgraded from v13 to v17 to maintain security and compatibility.
• TypeScript: Updated from v4 to v5.2.2 to align with Angular 17 requirements.
• core-js: Migrated from v2 to v3, updating all references to use modern es modules instead of deprecated es6 paths.

Key Adjustments:

Polyfills: Updated polyfills.ts to support core-js@3 with es module imports, ensuring compatibility with newer Angular configurations.
Testing Enhancements: Resolved issues in test.ts related to outdated configurations, enabling Karma to find all test files without manual imports.
Command Optimization: Added --watch=false to ng test due to recurring errors in watch mode. Other users also had this error, I followed their instructions to update packages, but after that didn't work, I ended up with this fix.
IE11 Support Removal: Removed support for Internet Explorer 11, as it is deprecated and unsupported by core-js@3.

Minor Changes:

Updated Angular.json Properties: Refactored to use updated Angular properties for improved build configurations.
TypeScript Target: Set target to ES2022 for enhanced compatibility with modern JavaScript standards.

[dr-bizz]

Look like I need to update the node version to node 18

[stage-branch-merger]

I see you added the "On Staging" label, I'll get this merged to the staging branch!

[stage-branch-merger]

Merge conflict attempting to merge this into staging. Please fix manually.

[dr-bizz]

@caleballdrin I have assigned this to you as you have worked on this before, but just let me know if I also need to get Caleb Cox or Daniel Frett.

[stage-branch-merger]

Merge conflict attempting to merge this into staging. Please fix manually.

[frett]

@dr-bizz any reason that there is both a package-lock.json and yarn.lock file? I'd assume we probably only want to use one package manager and not both.

But my js knowledge is limited, so there very well could be a good reason I don't know

[dr-bizz]

@dr-bizz any reason that there is both a package-lock.json and yarn.lock file? I'd assume we probably only want to use one package manager and not both.

But my js knowledge is limited, so there very well could be a good reason I don't know

We can remove the yarn.lock, I added that by mistake.

[frett]

@dr-bizz I think it was the other way, we had yarn.lock before and the package-lock.json is the new one :)

[dr-bizz]

Sorry, I just saw that.