api:Create local custom rule warning when using absolute import

[galethil]

Checklist

• I have followed (at least) the PR section of the contributing guide.
• I fixed all necessary PR warnings
• The commit history is clean
• The E2E tests are passing
• If possible, the issue has been divided into more subtasks
• I did a self review before requesting a review from another team member

Description

Custom eslint rule warning for /api when using absolute import

How to test

1. Run npm run lint or check code if eslint is setup in VSCode
2. On absolute imports and packages not mentioned in package.json a warning is created

Closes #1994

[openkfwCI]

	Notes	Time
✅	Note for Reviewer: E2E tests on pipeline 60490 on remote server succeeded	Wed, 02 Oct 2024 09:14:34 +0000

Generated by E2E-Test

[MartinJurcoGlina]

I would do the same for the rest of the services as well to keep eslint rules consistent

[SamuelPull]

Nice work! I'm not sure if this is needed anymore, updating tsconfig disables relative imports.