feat: add process discovery tests

[dmehala]

Motivation

Test process discovery feature. RFC

Changes

• Add a new parametric test.
• Update parametric tests internal.

Reviewer checklist

• If PR title starts with [<language>], double-check that only <language> is impacted by the change
• No system-tests internal is modified. Otherwise, I have the approval from R&P team
• CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
• A docker base image is modified?
  • the relevant build-XXX-image label is present
• A scenario is added (or removed)?
  • Get a review from R&P team

[cbeauchesne]

Keys must be ordered, this line should go few lines below

[dmehala]

is there a tool to automate that?

[cbeauchesne]

Unfortunately not 😞

It in our backlog, but lack of ressource ... #1722

[dmehala]

🫠 I'll write the tool tomorrow then.

[bm1549]

There are a ton of off the shelf tools for this, eg https://github.com/marketplace/actions/yaml-lint

For the above, we could use mostly default settings and enable the key-ordering rule
https://yamllint.readthedocs.io/en/stable/configuration.html#default-configuration

[cbeauchesne]

That would be awesome ❤️ . I've precised in the issue what to do

[dmehala]

Unfortunately, @cbeauchesne, I’ve decided to step away from writing the formatter due to more pressing priorities. At first I thought it would be as straightforward as calling a yaml formatter but the order requirement makes it more involved. Additionally, I find the order requirements to be primarily aesthetic and somewhat unclear.

[cbeauchesne]

@bm1549 is tacking the format/lint in #4077 🥳

Additionally, I find the order requirements to be primarily aesthetic and somewhat unclear.

The only reason for this requirements is to help people editing a lot manifests files: it helps finding a key. Though, I'm not attached at all to this requirements (i almost never edit those files). You can propose to remove this requirements on slack on #apm-shared-testing.