chore: bump OpenResty to v1.21.4.2

[tao12345666333]

What this PR does / why we need it:

OpenResty v1.21.4.2 has been released.

https://openresty.org/en/ann-1021004002.html

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• CVE Report (Scanner found CVE and adding report)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

Which issue/s this PR fixes

How Has This Been Tested?

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added unit and/or e2e tests to cover my changes.
• All new and existing tests passed.

[netlify]

✅ Deploy Preview for kubernetes-ingress-nginx canceled.

Name	Link
🔨 Latest commit	a9e8297
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-ingress-nginx/deploys/64b8a0144d8ef70008c15f11

[strongjz]

/priority backlog
/triage accepted
/ok-to-test
/kind feature

[strongjz]

/cherry-pick release-1.8

[k8s-infra-cherrypick-robot]

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

In response to this:

/cherry-pick release-1.8

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.

[strongjz]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: strongjz, tao12345666333

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:

• images/OWNERS [strongjz,tao12345666333]

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

[k8s-infra-cherrypick-robot]

@strongjz: #10219 failed to apply on top of branch "release-1.8":

Applying: chore: bump OpenResty to v1.21.4.2
Using index info to reconstruct a base tree...
M	images/nginx/rootfs/build.sh
Falling back to patching base and 3-way merge...
Auto-merging images/nginx/rootfs/build.sh
CONFLICT (content): Merge conflict in images/nginx/rootfs/build.sh
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 chore: bump OpenResty to v1.21.4.2
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:

/cherry-pick release-1.8

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.

[tao12345666333]

@strongjz @rikatz I know why it cannot be cherry-picked to v1.8. It's because this commit was made after removing the AJP module, which caused conflicts.

This should be considered a security update version of OpenResty. (But in fact, it also includes some feature updates.)

Do we need to cherry-pick it into v1.8? If necessary, I can manually cherry-pick it.