m3api-oauth2

• BREAKING CHANGE: m3api-oauth2 now requires at least Node.js version 18.2.0, up from Node 12.22.0 or Node 14.17.0 previously. As part of this, the m3api-oauth2/requireCrypto request option has been removed, as we no longer support any platform where the Web Crypto API is not available: it is now always used unconditionally.
• Updated dependencies.

Auto-refresh \o/

• The access token is now refreshed automatically; it is no longer necessary to call refreshOAuthSession() by hand, and sessions should
  remain usable indefinitely.
• Updated dependencies.

No code changes from v0.1.0, just a fix to the GitHub Actions workflow pushing the release to npm. (v0.1.0 could not be pushed to npm, unfortunately.)

To reiterate, v0.1.0 and v0.1.1 include:

• The OAuthClient class and initOAuthSession() and completeOAuthSession() functions, to perform the OAuth 2.0 authorization code flow.
• The refreshOAuthSession() function, to perform the refresh flow (albeit not yet automatically).
• The serializeOAuthSession() and deserializeOAuthSession() functions, to serialize the OAuth state of a session between requests.
• PKCE support, for non-confidential clients without a client secret.

Initial release, including:

• The OAuthClient class and initOAuthSession() and completeOAuthSession() functions, to perform the OAuth 2.0 authorization code flow.
• The refreshOAuthSession() function, to perform the refresh flow (albeit not yet automatically).
• The serializeOAuthSession() and deserializeOAuthSession() functions, to serialize the OAuth state of a session between requests.
• PKCE support, for non-confidential clients without a client secret.