Re-organize the code

[chaen]

The __init__.py contains too much code, but we agree we want to avoid the extreme of one class per file (from JobDB import JobDB style).
The current consensus would be like that:

• at a package level (router for example) we have one file per system (configuration.py for example)
• If we need more files (think of jobs, which have the sandbox, the joblogging, etc), we put them in a sub module (e.g routers.job). The code goes in a specific file (job.py, joblogging.py) but we use the the __init__.py to expose the specific file

[fstagni]

Right now, I see that https://github.com/DIRACGrid/diracx/blob/main/diracx-routers/src/diracx/routers/job_manager/__init__.py contains the code of what in DIRAC was JobManager and JobMonitor handlers. The only other WMS related router created is https://github.com/DIRACGrid/diracx/blob/main/diracx-routers/src/diracx/routers/job_manager/sandboxes.py.

Do I understand correctly that you would prefer to re-organize in a way similar to what is done for auth ? (https://github.com/DIRACGrid/diracx/blob/main/diracx-routers/src/diracx/routers/auth/__init__.py)

[ryuwd]

#296 will split the job manager handlers across more than one file