Feature: Add Include/Exclude Class regular expression matcher

[ying-jeanne]

What's being changed:

/claim #2481

Never used bounty before, just for fun, thank you for building this nice project.

This PR aims to address issue #2481.

I think it is just a bad idea trying to guess whether users intend to use an exact match or a regular expression. So in order to distinguish the intention and give more flexibility on settings, whether we could change include list to a list of struct:

{
  "include": [
      {
          "expression": "foo",
          "is_regex": false
      }
  ]
}

This approach offers clarity in distinguishing between exact matches and regular expressions. However, it may increase verbosity.

or adding a new array:

{
    "include_patterns": []{}
}

This alternative maintains backward compatibility with existing APIs and reduces verbosity. This PR use the second approach, if the direction seems ok, i would update docs and examples accordingly, please let me know.

Review checklist

• Documentation has been updated, if necessary. Link to changed documentation:
• Chaos pipeline run or not necessary. Link to pipeline:
• All new code is covered by tests where it is reasonable.
• Performance tests have been run or not necessary.

[algora-pbc]

💵 To receive payouts, sign up on Algora, link your Github account and connect with Stripe/Alipay.

[sonarcloud]

Quality Gate failed

Failed conditions
8.5% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud

[ying-jeanne]

add make format and make generate-code, I used them to fix CI.

[ying-jeanne]

After running make generate-code, sonar failed for duplication, i think we should exclude certain folder from duplication check. I am not very familiar with sonar code analysis config.