Hoist dependencies with Lerna and upgrade Nest.js

[nglgzz]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?

Hoist dependencies with Lerna to ensure that the Nest.js packages are installed only once, and upgrade Nest.js, typescript, and some other related dependencies.

What is the current behavior?

• Dependencies are installed multiple times across all packages.
• We use Nest.js 7.
• Each package generates its own package lock.

What is the new behavior?

• Dependencies are hoisted at the root of the project.
• We use Nest.js 8.
• Only one package lock is now maintained at the root of the project, all other package locks have been removed.
• There's a linting rule to ensure we don't import packages that aren't included in the package.json (More about that here)

Does this PR introduce a breaking change?

No

Other information:

As in the previous attempt to upgrade Nest.js, most of the changes in this PR are TypeScript, Eslint, and Prettier fixes.

[emmaagh]

All looks good to me! I tested linking the common package in desktop v1 & v2 and that all seemed to work as expected.

[emmaagh]

This formatting is so much better lol

[emmaagh]

Just noticed there's a conflict in 1 file FYI