build: upgrade ember-cli-typescript to v5.1.0

[ndekeister-us]

Build

Upgrade ember-cli-typescript to v5.1.0 (#195)

Also

• fix some new type errors
• add some @ts-ignore around getOwner code, see getOwner(this) returns unknown type typed-ember/ember-cli-typescript#1471

Chore

Run ember-cli-typescript blueprint (#195)

To be up to date with ember-cli-typescript config and recommandations in tsconfig.json

Running blueprints also add back @types/ember* packages in devDependencies, which solves a side effect introduced by #157.

• If we remove some @types/ember* packages from our devDependencies, they will still be included by other packages but they will resolve to a version sometimes incompatible with other @types/ember__* packages, resulting of type errors in build
• Keeping us sync with ember-cli-typescript ensure we don't face this issue again in this future

Example of build failing when we remove some @types/ember__x packages that we don't use (like routing, engine, array... ; even after a yarn-deduplicate && yarn):

Run yarn-deduplicate && yarn (#195)

Fix build and test by resolving @types/ember* packages to one single version in the yarn.lock (otherwise we would have sometimes two different versions for some @types/ember* packages, which would leads to type conflicts when building app

[MrChocolatine]

I wanted to take a look yesterday sorry, I will try this evening. (but I haven't forgotten, it is still in my todo-list)

[MrChocolatine]

A few comments and suggestions, but overall seems good to me, thanks for taking the time 👍 .

I trust you on the changes related to the "types" packages, I tried to make the upgrade on my side too and too many different errors (the entire tests suite would sometimes pass, sometimes not, something telling me our Initializer could not be found...).

And if for some reason we actually need every @types packages for Ember.js (those automatically shipped with ember-cli-typescript) then why not, it's not a big deal in the end).