feat: Added the mongodb exporter to the reference AWS/localhost deployments

[AncientPatata]

Motivation

• The exporter module was previously in the Infra but you had to add it in yourself to the reference deployment to use it.

Description

Added the MongoDB Exporter module to the reference AWS and localhost deployments.

Testing

Tested the different MongoDB deployments with the exporter (localhost,aws) (non-sharded on prem, sharded on prem, atlas). The Atlas MongoDB deployment was however only tested in localhost and not in an AWS deployment.

Impact

Given the relative simplicity of the database there shouldn't be much overhead when monitoring it. Still, moving up to v0.44 for the exporter comes with some performance improvements, fixes to bugs that made the exporter consume too much memory as well as addressing a major security vulnerability.

Additional Information

• This would also serve as a "how to deploy the mongodb exporter in your custom ArmoniK deployment" since it wasn't documented before.
• This PR depends on ArmoniK.Infra#250

Checklist

• My code adheres to the coding and style guidelines of the project.
• I have performed a self-review of my code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• I have thoroughly tested my modifications and added tests when necessary.
• Tests pass locally and in the CI.
• I have assessed the performance impact of my modifications.

[AncientPatata]

Deploy_localhost_AllInOne / coreStream (push) failing is not related to my PR

[lemaitre-aneo]

You need to change the infra version to 0.12.4 in versions.tfvars.json

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud