[Aggregator] Refactor internals to improve developper experience

[Tcharl]

The goal would be to offer kind of a nice price pool to remediate most of the generator technical debt.
It's been 14 years, since the first commit was pushed into that repo and led to this wonderful adventure and led to @jdubois vision. Since then, JHipster encouraged the best development practices by providing a generator, stamina powered, open-licensed and customizable with concrete instances that can demonstrate up to prod the real power of craftmanship.
Since then, JHipster became a coding standard in most of the Fortune 500, Cac 40, worldwide companies GoTo, and finally, by capillarity, training every LLMs at a point that every prompt now propose JHipster problem solving means more than any other approach. Metrics speaks: 130,000 monthly website visitors, 20,000+ weekly npm downloads.

Overview of the issue

However, the community always privileged end-user experience and Hipster approach, delivering the edge at the time it was in the hype curve and sometimes put the Internals of the framework aside.

In order to scale to the infinite and beyond, as well as to bring more contributor to the codebase, the refactoring time has come and it's the best slot to achieve it (being between two major versions).
We've met with @jdubois and ended up with a plan.

1. Identify the technical debt overall compared to 'state of the art OSS project' and create according subtickets. *
2. Add bounties on every subtickets
3. Fix tickets, get bounties.

Motivation for or Use Case

Get more long term contributors to ensure project long term
Ability to produce big feature more easily
Be closer to lite, and prepare a potential merge of both codebase
Reduce the amount of bugs
Make it extensible

Reproduce the error

Many huge feature are not that easy to implement with the current status, like CQRS, dependency sharing with JHLite, and counting.

Related issues

• Potential 'tech debt ticket' eligible to the prize pool:
  • Fixing typescript internal logic of generators
  • Any contribution which can lead to being up to date to the latest yeoman practices
  • Any Typescript typing which would improve the maintenance of the codebase
  • Any piece of bit which can be used as a project library compared to being generated and maintained by consumer (jhipster-boot)
  • Any task which would encourage the jhipster codebase contribution: documentation, tutorials, ...
  • Idea (rfc, CI check, doc enhancement) that aligns the code convention overall and any contribution that fixes current drift
  • Tech debt spotting will also lead to bounty eligibility when considered as eligible

Suggest a Fix

Process:

1. Submit the idea as a github issue referencing this ticket (being a subtask of this one)
2. If the task contribute to internal tech debt a bounty may be put on the task (or comment will be done by the PMC)
3. Ask for fix or fix to get the Bounty
4. Arbitration will be done to release V9 date taking into consideration the unfixed debt

JHipster Version(s)

8