Feat/use service with cache for reports

[Shelex]

Rationale

Issue:

• implementation of some features for better visualization will lead to heavier impact on network interaction (especially s3)
• working with huge s3 datasets causes a lot of querying under the hood
• results could be huge files 200+ Mb

Solution:

• as reports and results are just a static data, we can not only rely on client caching, but use in memory cache on backend

- UI -> Client cache -> Api route -> Storage -> S3/FS
+ UI -> Client cache -> Api route -> Service -> Cache/Storage -> S3/FS

To make it simple stupid, plain Map<string, entity> should work fine, so no database would be required in the app setup.

• this allows us to have all parsed report data in the response and in future provide more data to the ui and quickly

• this allows us to make interaction with s3 storage much efficient and avoid unnecessary queries

• instead of reading entire file from formData into memory, utilize streams

Demo

S3

• https://pw-s3-cached.shelex.dev
• api token: 12345

FS

• https://pw-fs-cached.shelex.dev
• api token: 12345

BREAKING CHANGE

• bump requirement for node version to v20

Changes

• when generating reports we have a project name autocomplete which has reports just from selected results. however when you have results without project, to avoid typing manually or copy-paste it makes sense to provide report projects in the autocompletion list as well.
• minor changes due to eslint errors/warnings