[Orchestrator] - Review of the overall codebase and align file & classes to match Fusion Directory structure

Requirements

It would be better to have the same naming convention for the files names and classes to aligned ourself with FD core / plugins. Some internal methods are no longer required and could be simplified. Overall requirement : quick code review.

Descriptive title for this enhancement

[Orchestrator] — Review of the overall codebase and align file & classes to match Fusion Directory structure

Actual behavior

Development names are being used

Expected behavior

More production names following FD structure, such as .inc for library file and .php for endpoints files. Adding class_*. as well as removing none usable methodes. Some variables names could be more explicit.

Goal : having a better manageable code in order to properly and easily add multiple new endpoints / library.

Step by step description of new behaviour

Re-work on the overral structure as described above.

Benefits

Better structure, vision, ease to adapt and develop further endpoints and/or plugins.

Possible Drawbacks

None

Applicable Issues

None