rgw: change the way to livenessProbe and introduce readinessProbe (backport #8643)

[mergify]

This is an automatic backport of pull request #8643 done by Mergify.
Cherry-pick of 536b59e has failed:

On branch mergify/bp/release-1.7/pr-8643
Your branch is up to date with 'origin/release-1.7'.

You are currently cherry-picking commit 536b59ef0.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   cluster/charts/rook-ceph/templates/resources.yaml
	modified:   cluster/examples/kubernetes/ceph/crds.yaml
	modified:   cluster/examples/kubernetes/ceph/object-ec.yaml
	modified:   cluster/examples/kubernetes/ceph/object-openshift.yaml
	modified:   cluster/examples/kubernetes/ceph/object.yaml
	modified:   pkg/apis/ceph.rook.io/v1/types.go
	modified:   pkg/apis/ceph.rook.io/v1/zz_generated.deepcopy.go
	modified:   pkg/operator/ceph/config/livenessprobe.go
	modified:   pkg/operator/ceph/config/livenessprobe_test.go
	modified:   pkg/operator/ceph/object/spec.go
	modified:   pkg/operator/ceph/object/spec_test.go
	modified:   tests/integration/ceph_base_object_test.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .github/workflows/canary-integration-test.yml
	both modified:   tests/scripts/github-action-helper.sh

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/

[satoru-takeuchi]

I'll fix this conflict later.

[satoru-takeuchi]

The conflict will be fixed in #9080 .

[travisn]

btw you should be able to force push to the branch opened by the bot, but no problem to have the new PR if you prefer.

[satoru-takeuchi]

@travisn Oh, I've taughut this knowledge from you and have completely been forgot it at all.