Dependency Conflict typescript@"5.0.3" & awesome-typescript-loader@"^5.2.0"

**Describe the bug**
When running npm install locally, I get a dependency conflict when resolving the dependency tree

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: node-server-with-typescript@1.0.0
npm ERR! Found: typescript@5.0.3
npm ERR! node_modules/typescript
npm ERR! dev typescript@"5.0.3" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@"^2.7 || ^3" from awesome-typescript-loader@5.2.1
npm ERR! node_modules/awesome-typescript-loader
npm ERR! dev awesome-typescript-loader@"^5.2.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /Users/lennart/.npm/_logs/2023-06-19T11_22_57_010Z-eresolve-report.txt

**To Reproduce**
Steps to reproduce the behavior:
1. Clone the repository
2. Run npm install
3. See error

**Expected behavior**
Npm install is able to run without error

**Desktop (please complete the following information):**
- OS: [e.g. iOS] macOS
- Browser [e.g. chrome, safari] N/A
- Version [e.g. 22] 12.6.6

Start by inspecting the repository's npm dependency manifest and reproduce the conflict with npm install. Resolve the incompatibility between typescript@5.0.3 and awesome-typescript-loader@^5.2.0, then verify that a clean npm install completes without force or legacy-peer-deps.

Written by the indexing model from the issue text.