Load Contexts in Analyser via entry points

[tieneupin]

We have reached a point in Murfey's development where some of the Context classes that can be attached to Murfey's Analyser class require additional dependencies not present in the default installation. To keep the client-side installation as lean as possible, we need to break the import chain by not importing all the Context classes upon initialisation of the Analyser. They should only be imported and attached to the Analyser once file analysis has determined which Context is needed for that particular session.

This PR accomplishes this by setting up the Context classes as entry points and loading the appropriate one once the Analyser has identified the appropriate context for the workflow.

[codecov]

Codecov Report

❌ Patch coverage is 30.90909% with 38 lines in your changes missing coverage. Please review.
✅ Project coverage is 49.32%. Comparing base (cd967b5) to head (1fd74f2).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #763      +/-   ##
==========================================
- Coverage   49.46%   49.32%   -0.15%     
==========================================
  Files          92       92              
  Lines        9793     9813      +20     
  Branches     1283     1296      +13     
==========================================
- Hits         4844     4840       -4     
- Misses       4709     4723      +14     
- Partials      240      250      +10     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.