Ability to disable certificate verification during connecting to CS, update docs, and fix anonymizer failing tests

[melbeltagy]

• Docs: Update README and collector module's documentation
• Feat: Add ability to disable certificate verification during connecting to central server
• Fix: Stop using dictionary unpacking for single fields to fix failing tests in anonymizer module

Refs: OPMONDEV-181

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[melbeltagy]

@raits , this PR is minimized version of PR #111 that is focusing only on new feature and fix anomynizer's pipeline.
I've cherry picked some commits from PR #111 and added minor updates.
I'll use the PR #111 later to focus on replacing pycodestyle with ruff as a linter

[raits]

One comment, otherwise looks good to me.

[raits]

Currently I believe that and empty value also disables this. Since older installations wouldn't have the parameter, can me also have the same behavior in these cases?

[melbeltagy]

Please correct me if I'm wrong, but as per my understanding for this section in the documentation, an empty value would still verify the SSL certificate (since it's the default behavior).

The reason why I added the new feature of disabling certificate verification while connecting to central server (not security server), is because I had SSL enabled for the central server locally, but collector module was failing to verify the certificate and hence failing to start.

Perhaps I am missing something or had my collector misconfigured and that there is way (without my modifications to collector_module/opmon_collector/central_server_client.py) that I can disable the certificate verification during SSL connection?

[raits]

Ah yes, sorry, for some reason I thought this related to enabling / disabling mTLS. In this case I think it is fine.

And it is a good catch about the Central Server, it previously did not support HTTPS, only HTTP. That's why the X-Road Metrics code hasn't accounted for the HTTPS connection to the global configuration yet.