Fix chart to set deletionTimeout value actually read by config.go

[ptnapoleon]

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:

• In Use disruptionDeleteTimeout key correctly in values.yaml #798, I changed the values.yaml to match the key in configmap.yaml. It turns out, values.yaml was right and configmap.yaml was wrong 🤦 . I've aligned everything to match what's actually in config.go
  

  chaos-controller/config/config.go

  Line 45 in d7060a8

  DisruptionDeletionTimeout time.Duration `json:"disruptionDeletionTimeout"`

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:
  • x
  • locally.
  • as a canary deployment to a cluster.

[datadog-datadog-prod-us1]

Datadog Report

Branch report: phil/refix-chart
Commit report: 69c9e88

✅ chaos-controller: 0 Failed, 0 New Flaky, 666 Passed, 0 Skipped, 6m 46.65s Wall Time

[aymericDD]

Thanks for the fix 🙏