Fix dev mode

[AndreaBarbasso]

References

• Fixes Dev mode not working #4809

Description

Introduced the tsconfig-paths package (github, npm) to resolve TypeScript path aliases.

Instructions for Reviewers

The tsconfig-paths package hooks into the Node.js module resolution system and allows it to understand the path mappings from the tsconfig.json file.
The fix involved updating all ts-node commands in the scripts section of package.json to include the -r tsconfig-paths/register flag. This flag pre-loads the path mappings, enabling Node.js to correctly resolve the aliased module paths at runtime and successfully execute the scripts.

To test this PR, check that the project can run both in dev and prod mode with no issues.

Checklist

• My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• My PR passes ESLint validation using npm run lint
• My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
• My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
• My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
• My PR aligns with Accessibility guidelines if it makes changes to the user interface.
• My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
• My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
• If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
• If my PR fixes an issue ticket, I've linked them together.

[nwoodward]

👍 Thanks @AndreaBarbasso. This PR fixes the errors on those npm commands for me.

[tdonohue]

👍 Thanks @AndreaBarbasso ! I tested both prod mode and dev mode again. Both work well now, so this fixes the issues.