What does this PR do?

• 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:

• This PR aims to adapt the cpu-pressure injector to be able to react to container restarts
• This PR also fixes couple of bugs seen along the way:
  • Exit without error
  • Stress all containers not only the last
  • Stress all cores on all containers
  • split DisruptionInjectionStatus and DisruptionTargetInjectionStatus to avoid miss understanding of which is allowed to have what.
  • add some new DisruptionInjectionStatus to avoid having a misleading PreviouslyInjected status (when it was partially injected or not injected, an expired disruption changed to the same status, it's no longer the case)
  • fixes when the previously injection status is calculated to ensure when injection pods exited successfully near the deadline we are not transitioning back to PartiallyInjected

This PR also takes the opportunity to (re)-introduce a make local rule to run the controller outside of Kubernetes.
This PR also introduce a make pre-debug that will like make local except it won't launch the binary and will let you use you favorite debugger method (IDE, dlv, ...)

This PR also review how we are running e2e-test to guarantee pods are created for each test ran and ease their duplication.
E2E-tests are hence now ran in parallel.

Code Quality Checklist

• The documentation is up to date.
• My code is sufficiently commented and passes continuous integration checks.
• 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:
  • locally.
  • as a canary deployment to a cluster.