Refactoring Jim for an easier adoption for production in LVK

[kazewong]

Currently Jim is still in its adolescent stage, which it is usable and energetic but it is not very social and user friendly. To make Jim to be usable and more importantly hired by the community, we need to refactor Jim to have a cleaner API with some features useful for productions runs in the future.

Note that on the top level, while we want to be as user-friendly and modular as possible, this should not come with a cost to performance.

Here is a preliminary list of features needed for the refactoring and next release:

• API for setting priors #11
• Batch job submission #12
• Clean up interfaces for handling detectors #13
• Automated unit test for the classes #14
• Automated convergence test during run time. #15
• Minimize unnecessary package call. #16
• Data fetcher #17
• Command line tools for runs. #18
• Github action for pushing to pypi #19
• Documentation and examples #20

This should be the development main branch where the aforementioned features can be branched off from.