feat(config_visibility): enhanced config reporting [APMAPI-1693]

[vpellan]

What does this PR do?

This will send all the DD configs through telemetry, including the configs with lower precedence. This means that a config set through env var and code will be reported three times, (default, env_var and code) with the corresponding values. To differentiate the one with the highest precedence, we send a seq_id, and the highest seq_id is the currently active config.

Motivation

Additional Notes

Waiting for a new release of libdd-telemetry

[bantonsson]

I think the code has become a bit convoluted. I would like to know if it's ok to have gaps in the sequence ids, like this:

[
  { "name": "logs_injection_enabled", "origin": "default", "value": false, "seq_id": 1 },
  { "name": "logs_injection_enabled", "origin": "env_var", "value": true, "seq_id": 3 },
  { "name": "logs_injection_enabled", "origin": "code", "value": true, "seq_id": 4 }
]

Then the code could be simplified by using the ConfigSourceOrigin as the sequence id.

[vpellan]

Hey @bantonsson , thanks for your review! I applied your changes on 6f39ebe. I was so focused on getting the sequence id in the correct order that I did not realised that there could be gaps between them... The answer is yes and it does simplify the code.