Authz: node18 re-write

[sauntimo]

⚠️ WIP DO NOT MERGE

✏️ Changes

• Update the extension to run on node 18.16.0
• Bump underlying hapi.js framework to 21.3.3 which involved a huge number of changes because the whole framework has been re-written from using callbacks to using async/await.
• Many other related dependency version bumps, to get compatibility between peer dependencies. There are some limitations based on which versions of what packages can be included from https://auth0-extensions.github.io/canirequire/ - some specific package versions are not available and so are included in the bundle instead.
• fix functionality broken by package updates, which, essentially, was all of it
• fix all unit (144) and integration (34) tests. NB, integration tests currently work pointing at a layer0 dev space, I don't currently know if it will be possible to have these running locally successfully.

NOTES

• will only build with this UNMERGED branch of the auth0-extensions-cli: https://github.com/auth0-extensions/auth0-extensions-cli/pull/64
• check this branch out locally, then in the repo run npm link. Then navigate back to the authorization extension repo and run npm link auth0-extensions-cli. This will then use the local version of the extensions cli, not the master version.

📷 Screenshots

If there were visual changes to the application with this change, please include before and after screenshots here. If it has animation, please use screen capture software like to make a gif.

🔗 References

Include at at least one link to an explanation + requirements for this change, and more if at all possible. Typically this is a Jira/GitHub Issue, but could also be links to Zendesk tickets, RFCs, rollout plan or Slack conversations (for Slack conversations, make sure you provide a summary of the conversation under “Changes”).

🎯 Testing

Describe how this can be tested by reviewers. Please be specific about anything not tested and reasons why.

• Make sure you add unit and integration tests.
• If this is on a hot path, add load or performance tests
• Especially for dependency updates we also need to make sure that there is no impact on performance.

✅🚫 This change has been tested in a Webtask

✅🚫 This change has unit test coverage

✅🚫 This change has integration test coverage

✅🚫 This change has been tested for performance

🚀 Deployment

Can this change be merged at any time? What will the deployment of the change look like? Does this need to be released in lockstep with something else?

✅🚫 This can be deployed any time

or ⚠️ This should not be merged until:

• Other PR is merged because REASON
• After date because REASON
• Other condition: REASON

🎡 Rollout

Explain how the change will be verified once released. Manual testing? Functional testing?

In order to verify that the deployment was successful we will …

🔥 Rollback

Explain when and why we will rollback the change.

We will rollback if …

📄 Procedure

Explain how the rollback for this change will look like, how we can recover fast.

🖥 Appliance

Note to reviewers: ensure that this change is compatible with the Appliance.