Release needed for JupyterHub 2 and 3 compatibility

[consideRatio]

#160 was merged just after 1.0.5 was released, and we need a release including it for functionality with JupyterHub 2 and 3. The JupyterHub Helm chart in https://github.com/jupyterhub/zero-to-jupyterhub-k8s will include JupyterHub 3 so users of nativeauthenticator can't upgrade to it unless a patch is released.

Generating a changelog using github-activity I saw the following PRs merged since 1.0.5. Is any change here a breaking change that merits a 2.0.0 release? Otherwise, it should be a 1.1.0 release as it includes enhancements etc rather than just documentation/bugfixes.

1.0.5...master@{2022-08-25}

(full changelog)

Enhancements made

• Ask for new passwords twice, ask for current password on change #180 (@lambdaTotoro)

Bugs fixed

• Add slash restriction to username validation #197 (@marc-marcos)
• Correct login procedure for admins #195 (@lambdaTotoro)
• Enforce password criteria on password change #169 (@lambdaTotoro)
• Systematic refresh of templates #162 (@consideRatio)

Maintenance and upkeep improvements

• document and refactor the handlers #183 (@lambdaTotoro)
• chore: use async instead of gen.coroutine #178 (@consideRatio)
• pre-commit: apply black formatting #174 (@consideRatio)
• Smaller tweaks from pre-commit autoformatting hooks #173 (@consideRatio)
• Support JupyterHub 2's fine grained RBAC permissions, and test against Py3.10 and JH2 #160 (@consideRatio)

Documentation improvements

• update documentation screenshots #194 (@lambdaTotoro)
• docs: fix c.JupyterHub.template_paths #192 (@yapatta)
• docs: c.NativeAuthenticator instead of c.Authenticator #188 (@consideRatio)
• docs: update from rST to MyST and to common theme #187 (@consideRatio)
• document and refactor the handlers #183 (@lambdaTotoro)
• docs: add inline documentation to orm.py #179 (@consideRatio)
• Update CONTRIBUTING.md #161 (@consideRatio)

Continuous integration improvements

• ci: rely on pre-commit.ci & run tests only if needed #175 (@consideRatio)

[consideRatio]

@lambdaTotoro now JupyterHub 3.0.0 is out and z2jh 2.0.0 could be released today, but nativeauthenticator will be broken with that version bump of JupyterHub from JupyterHub 1 to JupyterHub 3 made in the z2jh distribution of JupyterHub.

Is it okay if I'll go for a release of nativeauthenticator 1.1.0 in its current state?

[lambdaTotoro]

Yes, go ahead. I would have liked to incorporate a few things still, but I didn't get to them in time and this is more important.