Tracking Issue: prepare for release 2.2.0, feature status

[STRRL]

We are going to release Chaos Mesh 2.2.0, we would cut the branch release-2.2 from master later, and there are still several uncompleted codes that exist on master, we should prune them.

Uncompleted features should be carried with 2.2.0:

• chaosctl forced recovery supports httpchaos, iochaos, stresschaos, and networkchaos #2992
• Tracking Issue: tidy helm chart #3015
• feat: next New Workflow in UI #3185
• update memStress #3186

Uncompleted features/enhancements skewed to next minor/patch version:

• Guide and example manifests for monitoring chaos mesh #3030 No necessary must carried with 2.2;
• timechaos support arm64 #2634 require more time to review, delayed to the next minor version.
• JVMChaos: support inject fault into MySQL client #3189 require more time to test and review +1, delayed to the next minor/patch version.
• Full automation between OpenAPI and front-end #2822 There is no work left that would block the 2.2.0, resting work is about improving performance, which might be carried in the next minor release.

Features need to prune:

• BlockChaos
• ...

Known issues:

• DNSChaos experiment don't work as intended when multiple chaos-dns-server pods are available #2409