feat: verify mocks in the CI

[aymericDD]

What does this PR do?

• [x] Adds new functionality
• [ ] Alters existing functionality
• [ ] Fixes a bug
• [ ] Improves documentation or testing

Please briefly describe your changes as well as the motivation behind them:

• Verify if mocks are updated.

Code Quality Checklist

• [x] The documentation is up to date.
• [x] My code is sufficiently commented and passes continuous integration checks.
• [x] I have signed my commit (see Contributing Docs).

Testing

• [ ] I leveraged continuous integration testing
  • [ ] by depending on existing unit tests or end-to-end tests.
  • [ ] by adding new unit tests or end-to-end tests.
• [ ] I manually tested the following steps:
  • x
  • [ ] locally.
  • [ ] as a canary deployment to a cluster.

[datadog-datadog-prod-us1[bot]]

Datadog Report

Branch report: feat/verify-mock-ci Commit report: 1896444 Test service: chaos-controller

:white_check_mark: 0 Failed, 970 Passed, 2 Skipped, 22m 59.14s Total Time :snowflake: 1 New Flaky

New Flaky Tests (1)

• [It] Disruption Controller don't reinject a static node disruption when chaos pods doesn't exist for injected targets should not recreate those chaos pods - Controller Suite - Last Failure

  Expand for error

  imed out after 211.638s.
  xpected success, but got an error:
     <*errors.errorString | 0xc000c82710>: 
     chaos pods count is not equal to expected count: 0 != 2
     {
         s: "chaos pods count is not equal to expected count: 0 != 2",
     }
  
  FAILED] Timed out after 211.638s.
  xpected success, but got an error:
  ..