[e2e] verifying LimitRange update is effective before creating new pod

[dixudx]

What this PR does / why we need it:
Refer to the flaky test mentioned in #68170, LimitRange updating should be verified before creating new pod.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #68170

Special notes for your reviewer:
/cc bsalamat k82cn
/sig scheduling

Release note:

[e2e] verifying LimitRange update is effective before creating new pod

[dixudx]

/assign timothysc

[k82cn]

/assign
/unassign timothysc

I'll help to review that :)

[bsalamat]

/lgtm

Thanks, @dixudx!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bsalamat, dixudx

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:

• test/e2e/scheduling/OWNERS [bsalamat]

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

[spiffxp]

/milestone v1.12
/priority critical-urgent
SIG Testing chair, this fixes a flake, and had the appropriate reviews prior to freeze

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel comment for consistent failures.

[k8s-github-robot]

/test all [submit-queue is verifying that this PR is safe to merge]

[dixudx]

/retest

[k8s-github-robot]

Automatic merge from submit-queue (batch tested with PRs 68171, 67945, 68233). If you want to cherry-pick this change to another branch, please follow the instructions here: https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md.