chore: 🤖 upgrade to angular v18

[chimurai]

BREAKING CHANGE: 🧨 Angular 18

• npm run update
• npm install --force
• npm run migrate
• fix: Invalid self-closing element in index HTML file: '<app-root />'.
• npm i -D @jscutlery/semver@latest --save-exact
• bump @ngneat/spectator to v19
• npm audit fix (15 vulnerabilities (11 moderate, 4 high))

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/ngneat/transloco/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Angular 17

Issue Number: N/A

What is the new behavior?

Angular 18

Does this PR introduce a breaking change?

• Yes
• No

Other information

closes: #734

[shaharkazaz]

@chimurai Thanks for the PR! why we need to force install?

[chimurai]

That was due to dependency conflicts after npm run update and npm install:

Happy to hear if there is a better way.

[shaharkazaz]

@chimurai The solution is to resolve the conflicts 🙂
I'll give it a go locally to see what's up

[chimurai]

Found the issue.
Bit confusing message from nx after running npm run update
Running npm install caused all the dependency conflict messages.

npm install or npm install --force is not needed when running these two commands sequentially:

npm run update
npm run migrate

Will open a new PR without npm install --force

[chimurai]

new PR without npm install --force: #775