Automated cherry pick of #2025: Make the defaults for PodsReady backoff more practical

[mimowo]

Cherry pick of #2025 on release-0.6.
#2025: Make the defaults for PodsReady backoff more practical
For details on the cherry pick process, see the cherry pick requests page.

Make the defaults for PodsReadyTimeout backoff more practical, as for the original values
the couple of first requeues made the impression as immediate on users (below 10s, which 
is negligible to the wait time spent waiting for PodsReady). 

The defaults values for the formula to determine the exponential back are changed as follows:
- base `1s -> 10s`
- exponent: `1.41284738 -> 2`
So, now the consecutive times to requeue a workload are: 10s, 20s, 40s, ...

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue ready!

Name	Link
🔨 Latest commit	c029e44
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-kueue/deploys/66269e254115470008705101
😎 Deploy Preview	https://deploy-preview-2033--kubernetes-sigs-kueue.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[mimowo]

/assign @tenzen-y @alculquicondor

[tenzen-y]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 55dd9b63a11c64898c78dcee57c01219f272f5f6

[alculquicondor]

/lgtm
/approve

[tenzen-y]

/release-note-edit

Make the defaults for PodsReadyTimeout backoff more practical, as for the original values
the couple of first requeues made the impression as immediate on users (below 10s, which 
is negligible to the wait time spent waiting for PodsReady). 

The defaults values for the formula to determine the exponential back are changed as follows:
- base `1s -> 10s`
- exponent: `1.41284738 -> 2`
So, now the consecutive times to requeue a workload are: 10s, 20s, 40s, ...

[tenzen-y]

It seems that we need to merge #2034 first.
/hold

[alculquicondor]

I don't think release-0.6 was affected

[mimowo]

0.6 wasn't affected, that's why I needed to push the additional commit

[alculquicondor]

/lgtm
/approve
/hold cancel

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 0eee98542050ffaf3bad9abb97dcd9e7b1a4cc0b

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alculquicondor, mimowo, tenzen-y

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 [alculquicondor,tenzen-y]

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

[alculquicondor]

/kind bug