Migrate scripts from OpenResty to NJS

[elizabeth-dev]

What this PR does / why we need it:

Work in progress... Will update description eventually, meanwhile, here's what has been migrated:

• more_set_headers and more_clear_headers
• set_escape_uri
• auth_digest
• substitution
• external_auth
• auth cache key
• server redirects

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

fixes #12383

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: elizabeth-dev
Once this PR has been reviewed and has the lgtm label, please assign tao12345666333 for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

[k8s-ci-robot]

Hi @elizabeth-dev. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[netlify]

✅ Deploy Preview for kubernetes-ingress-nginx canceled.

Name	Link
🔨 Latest commit	0c91114
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-ingress-nginx/deploys/67499d133b5dc700082acb0b

[longwuyuan]

cc @rikatz

[rikatz]

@elizabeth-dev I will try to review it this or next week (sorry, full queue here).

Can we do separated PRs for each migrated feature? This way, if something bad happens is easier to revert just one :D

[elizabeth-dev]

@elizabeth-dev I will try to review it this or next week (sorry, full queue here).

Can we do separated PRs for each migrated feature? This way, if something bad happens is easier to revert just one :D

@rikatz thanks, and no worries!

and sure, I'll open a separate PR for each feature, along with one for adding NJS itself.

[elizabeth-dev]

/close as a separate PR will be opened for each migrated feature