Include server start time in INFO output.

Having the 'samode' capability made all KICK commands privileged. This appears
to have been introduced unintentionally by 42316bc04f and I can't find
any discussion of a rationale. Since this goes against our policy that all
ircop (as opposed to channel founder) privileges must be invoked explicitly
(e.g. SAJOIN, SAMODE), remove this.

This extends #1650 to cover WHO as well as WHOIS

The arithmetic was assuming that the nickname is * (which it is
pre-registration). However, we were sending the actual nickname
post-registration. It would be simpler to always send *, but it
appears that the nickname is actually required by the spec:

>Replies from the server must [sic] contain the client identifier name or
>asterisk if one is not yet available.

Jobe points out that 0 is a valid oplevel in some contexts,
* is a better placeholder for "unimplemented".

See discussion on #1852

From discussion with @emersion, this will help with UX if people try to
log into their unverified accounts.

Account registrations pending verification should produce a logline and
send a sno.

Reported by @mogad0n; the mute mask was being case-canonicalized,
but the RELAYMSG identifier wasn't being case-canonicalized before
the check.

`WHO #channel o` is supposed to return only server operators.
This is RFC1459 cruft; just return an empty list in this case.

RPL_ENDOFWHO should send the original, un-normalized mask

Ensure the pagination window is full by making sure that every history item
gets a replay line in CHATHISTORY output, even TAGMSG.

This reverts commit 5bbee02fe6.

Fix various pagination issues with CHATHISTORY; also undo #491
(msgid munging).

Fixes #1787

Warn if the user sent, e.g., /QUOTE /SAMODE instead of /QUOTE SAMODE

Refs:

* other instances in the codebase
* https://defs.ircdocs.horse/defs/numerics.html#err-needmoreparams-461
* https://modern.ircdocs.horse/#errneedmoreparams-461

For consistency with RFC2812, Bahamut, Hybrid, Insp, Plexus4, Unreal.
https://datatracker.ietf.org/doc/html/rfc2812#section-3.2.8

At the expense of consistency with chary/solanum, irc2, and ircu2.

reported by @Mikaela

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

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

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

CHATHISTORY INVALID_TARGETS was missing the subcommand parameter

It could be the real IP or the proxied IP.

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

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.

Remove the CHATHISTORY * and znc.in/playback *self targets,
clean up associated database code, add new mechanisms to play
all missed DMs.

Remove debugging loglines for truncation

Implements the new `CHATHISTORY LISTCORRESPONDENTS` API.

All truncation must be made UTF8-safe.

AWAY status should be tracked per-session:

1. With auto-away enabled, away status is aggregated across sessions
   (if any session is not away, the client is not away, else use
   the away status that was set most recently)
2. With auto-away disabled, we get the legacy behavior where AWAY
   applies directly to the client

Implement the new bot mode spec:
https://github.com/ircv3/ircv3-specifications/pull/439