refacto(plugin): apply git hooks against existing codebase

[Guts]

In this PR, I basically ran pre-commit run -a and made some manual cleanup to comply with rules introduced with git hooks.

Some questions @kannes:

• is there a specific reason to use a different case for naming certain modules: userInterface, interface_handler.py, Bookmarks...
• have the tests already been played? They look like those generated by pb (plugin builder), right? If so, we should remove them, no?
• what's the point of darkedetect subpkg?

---

• Related to Profile Manager x QGIS Deployment Toolbelt: an impacting contribution proposal #10
• ❤️ Funded by Oslandia and ANFSI.

[kannes]

• is there a specific reason to use a different case for naming certain modules: userInterface, interface_handler.py, Bookmarks...

Nope, feel welcome to harmonize all that.

• have the tests already been played? They look like those generated by pb (plugin builder), right? If so, we should remove them, no?

Agreed, there is nothing of use in that directory. If I'd set up tests, I would use pytest.

• what's the point of darkedetect subpkg?

I think the original developer wanted an automatic switch to a dark UI theme. I'd say throw it all away :)

[Guts]

Thanks for your answers.

I'll dot those changes in future PRs. You can review and (hopefully) merge this one.

[kannes]

👍 looks good!