feat: extension management

[aldbr]

Here we try to stabilize the repo:

Project management:

• drop lerna: it was only used to run diracx-web-components and diracx-web concurrently in dev mode (tsup --watch and next dev). Running both processes in parallel was cpu-intensive. Instead of that, we use the transpile option of NextJS instead (NextJS is responsible for cross compiling diracx-web-components when needed). Therefore, only 1 process is used for both workspaces in dev mode.
• restructure diracx-web-components by adding the components in a /src directory.
• move every packages from CJS to ESM
• upgrade to ESLint 9, because 8 was deprecated. This also involved upgrading to NextJS 15 and consequently to MUI 6, this was a significant upgrade.
• add/update documentation:
  • user guide
  • dev guide
  • admin guide

Gubbins

• add a basic test for the extension, just to make sure the login page can load fine and the user can login. This will prevent merging not compatible PRs 🙃
• add gubbins in the npm workspaces so that it uses a local version of diracx-web-components
• add a github workflow for the extension as an example.
• make new gubbins application to match gubbins backend services.
  • create a complete new application (adding a new Owner)
  • reuse an inner component (DataTable) to create a new component (OwnerMonitor)
  • use a component with different parameters (JobMonitor): may be it would be easier by adding a new parameter in the gubbins JobDB.

Needs:

• feat: improve datatable #238
• feat(diracx-web): support npm workspaces diracx-charts#124

Would be good to have:

• fix(diracx-web): support absolute paths diracx-charts#125

[ryuwd]

LGTM! I looked through all the files and while this is a big PR I see that many of the changes involve sensible reorganisation of files and refactoring. The documentation added here is thoughtful and well written.