Split components to better identify (core, library APIs) and (schedulers)

This is a tracking issue for the reorganization of pybatsim architecture. Once completed, we should have a clear separation of

• core logic (communication with Batsim) and base API
• officially maintained schedulers

Unmaintained schedulers, and schedulers with a very narrow domain should be correctly identified. The new architecture should present everything under the unique namespace pybatsim.

changed milestone to %PyBatsim 4

The PyPA guides are a great documentation source. In particular, see:

• https://packaging.python.org/en/latest/guides/creating-and-discovering-plugins/
• https://packaging.python.org/en/latest/guides/packaging-namespace-packages/

mentioned in merge request !16 (merged)

As much as possible, these modifications should impact code organization and not code usage.

We should be able to re-run the following examples:

• https://gitlab.inria.fr/batsim/bebida-on-batsim/-/blob/master/experiments/bebida-exp-replay/Bebida_on_batsim_simulation.ipynb
• … add more as users send them to me!

A proposition of plugin API is up and live in !16 (merged). It stills needs to be documented though.

What needs to be documented:

• how to use: documentation + tutorial and a companion repository (cf. #21 (closed))
• define a naming convention (base-variant looks reasonable)

assigned to @bleuse