We can check once during initialization of the SASL session, e.g.
on receiving `AUTHENTICATE PLAIN` or `AUTHENTICATE EXTERNAL`

Fixes #1762

See: https://github.com/ircv3/ircv3-specifications/pull/466

A default channel mode of +i would block channel creation; fix this by treating
initial joins as SAJOINs.

Note that it's nontrivial to detect initial join in (*Channel).Join, because
having 0 members does not necessarily indicate a new channel.

Allow SAJOIN or implicit always-on join to override channels.operator-only-creation

RENAME (channel rename) that was a simple case change (e.g.
renaming #chan to #CHAN) would delete the channel :-|

This is one of the two cases of [RFC 2812 kicks](https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.8):
even when there are multiple user targets, the RFC (and Unreal
and Inspircd and probably others) allows a single channel name.

Fixes #1740

See #1659

Fix error message for privileged NS PASSWD on a nonexistent account

May help clarify TLS configuration issues, possibly others too

Fixes #1733

CHATHISTORY INVALID_TARGETS was missing the subcommand parameter

Validate operator vhosts against the configured (or default)
vhosts.valid-regexp

Fix a panic if the operator class title is empty

It could be the real IP or the proxied IP.

`WHOWAS :` should return an error numeric instead of an empty response

Co-authored-by: Mikaela Suomalainen <mikaela@mikaela.info>

fix help for +f mode

Commit 7ce396931c introduced the ability
that every user with an account in the AMODE list of a channel can use
the OP command to restore their modes. Update the chanserv help message
accordingly.

Users logged into an account can see their own email.
Opers with the accreg capability can see all users.

Sort snomasks for display rather than displaying them in hash order

This is a regression introduced in 0d05ab4ff4; playback for an individual
DM target would play all DMs.

If the relay bot and the owner share an IP, legacy bots that identify users
by user@host could misinterpret relayed lines as coming from the bot owner.
Try to avoid this by using the bot's account cloak where applicable.

Send a full NUH with RELAYMSG.

Also fix client-only tags with RELAYMSG.