refactor: optimize allInjected and allRecovered states

[g1eny0ung]

What problem does this PR solve?

Optimize allInjected and allRecovered states when targets are not selected.

Before:

2023-09-16T02:51:42.517Z	INFO	condition	condition/controller.go:122	updating conditions
{"conditions": [{"type":"Paused","status":"False"},{"type":"Selected","status":"False"},{"type":"AllInjected","status":"True"},{"type":"AllRecovered","status":"True"}]}

After:

2023-09-16T03:57:50.937Z	INFO	condition	condition/controller.go:132	updating conditions
{"conditions": [{"type":"Paused","status":"False"},{"type":"Selected","status":"False"},{"type":"AllInjected","status":"False"},{"type":"AllRecovered","status":"False"}]}

What's changed and how it works?

Instead of arbitrarily setting the initial values of allInjected and allRecovered, the value is assigned based on the current selected state.

Related changes

• This change also requires further updates to the website (e.g. docs)
• This change also requires further updates to the UI interface

Cherry-pick to release branches (optional)

This PR should be cherry-picked to the following release branches:

• release-2.6
• release-2.5

Checklist

CHANGELOG

Must include at least one of them.

• I have updated the CHANGELOG.md
• I have labeled this PR with "no-need-update-changelog"

Tests

Must include at least one of them.

• Unit test
• E2E test
• Manual test

Side effects

• Breaking backward compatibility

DCO

If you find the DCO check fails, please run commands like below (Depends on the actual situations. For example, if the failed commit isn't the most recent) to fix it:

git commit --amend --signoff
git push --force

[g1eny0ung]

/cherrypick release-2.6

[chaos-mesh-cherrypick-robot]

@g1eny0ung: once the present PR merges, I will cherry-pick it on top of release-2.6 in a new PR and assign it to you.

In response to this:

/cherrypick release-2.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[codecov]

Codecov Report

Merging #4199 (45f6f17) into master (466578e) will decrease coverage by 0.07%.
Report is 3 commits behind head on master.
The diff coverage is 70.49%.

@@            Coverage Diff             @@
##           master    #4199      +/-   ##
==========================================
- Coverage   38.43%   38.36%   -0.07%     
==========================================
  Files         167      169       +2     
  Lines       13787    13900     +113     
==========================================
+ Hits         5299     5333      +34     
- Misses       8052     8131      +79     
  Partials      436      436              

Files	Coverage Δ
controllers/common/step.go	0.00% <0.00%> (ø)
controllers/common/condition/controller.go	46.23% <79.62%> (ø)

... and 3 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4e3ee29...45f6f17. Read the comment docs.

[cwen0]

LGTM

[cwen0]

/lgtm

[chaotic-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cwen0

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [cwen0]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[chaotic-prow]

New changes are detected. LGTM label has been removed.

[chaos-mesh-cherrypick-robot]

@g1eny0ung: #4199 failed to apply on top of branch "release-2.6":

Applying: refactor: allInjected and allRecovered conditions
Applying: chore: update
Using index info to reconstruct a base tree...
M	CHANGELOG.md
Falling back to patching base and 3-way merge...
Auto-merging CHANGELOG.md
CONFLICT (content): Merge conflict in CHANGELOG.md
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0002 chore: update
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-2.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.