Upgrade all JavaScript dependencies

[wallrj]

Preview: https://deploy-preview-1156--cert-manager-website.netlify.app/

I've upgraded to nextjs 13 and also upgraded all the other dependencies in package.json.
This required some (mostly machine generated) changes to the code.

See comments below for more context.

[netlify]

✅ Deploy Preview for cert-manager-website ready!

Name	Link
🔨 Latest commit	514e8c5
🔍 Latest deploy log	https://app.netlify.com/sites/cert-manager-website/deploys/63c6715e8342e200083ecd13
😎 Deploy Preview	https://deploy-preview-1156--cert-manager-website.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 settings.

[wallrj]

In addition to the remarks below, I ran npm shrinkwrap which resulted in the renaming of package-lock.json → npm-shrinkwrap.json

This seems to be best practice for npm applications (versus libraries) but I may have misunderstood:

• https://docs.npmjs.com/cli/v9/configuring-npm/npm-shrinkwrap-json/

[inteon]

In addition to the remarks below, I ran npm shrinkwrap which resulted in the renaming of package-lock.json → npm-shrinkwrap.json

This seems to be best practice for npm applications (versus libraries) but I may have misunderstood:

• https://docs.npmjs.com/cli/v9/configuring-npm/npm-shrinkwrap-json/

I think npm-shrinkwrap.json is only useful when you are talking about libraries:
https://medium.com/@hossam.hilal0/package-json-vs-package-lock-json-vs-npm-shrinkwrap-json-33fcddc1521a

Thus:
If you are not publishing your package to npm, the choice between these two files
is of little consequence. You may wish to use package-lock.json because it is the default
and its name is clearer to npm beginners; alternatively, you may wish to use npm-shrinkwrap.json
for backwards compatibility with npm 2-4 if it is difficult for you to ensure everyone
on your development team is on npm 5+. (Note that npm 5 was released on 25th May 2017;
backwards compatibility will become less and less important the further we get from that
date, as most people will eventually upgrade.)

[wallrj]

I think npm-shrinkwrap.json is only useful when you are talking about libraries:
https://medium.com/@hossam.hilal0/package-json-vs-package-lock-json-vs-npm-shrinkwrap-json-33fcddc1521a

Agreed. I've reverted that change.

PTAL

[inteon]

Thank you for upgrading!
/lgtm
/approve

[jetstack-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: inteon, wallrj

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 [wallrj]

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