refactor(init): code cleanup and better test coverage

[bearomorphism]

Description

Checklist

• I have read the contributing guidelines

Code Changes

• Add test cases to all the changes you introduce
• Run poetry all locally to ensure this change passes linter check and tests
• Manually test the changes:
  • Verify the feature/bug fix works as expected in real-world scenarios
  • Test edge cases and error conditions
  • Ensure backward compatibility is maintained
  • Document any manual testing steps performed
• Update the documentation for the changes

Documentation Changes

• Run poetry doc locally to ensure the documentation pages renders correctly

Expected Behavior

Steps to Test This Pull Request

Additional Context

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.41%. Comparing base (a9cd957) to head (233b55d).

Additional details and impacted files

@@              Coverage Diff              @@
##           refactors    #1424      +/-   ##
=============================================
+ Coverage      97.87%   98.41%   +0.54%     
=============================================
  Files             57       57              
  Lines           2677     2656      -21     
=============================================
- Hits            2620     2614       -6     
+ Misses            57       42      -15     

Flag	Coverage Δ
unittests	98.41% <100.00%> (+0.54%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

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

[bearomorphism]

test_pre_commit_not_installed is not working as expected...

[bearomorphism]

Does the order of these configs matter here?

[woile]

Nop

[bearomorphism]

Thanks.

[woile]

Ideally, the VersionProvider ABC class should include identifier and description. Which would allow us to do something like

providers = metadata.entry_points(group=PROVIDER_ENTRYPOINT)

{provider.identifier: provider.description for provider in providers} 

This way, custom user made providers would also appear in the init functions.

---

Just to be clear, this is optional, I hardcoded them here because it would help 90% of the users and I didn't want to go further.