rules: drop draft/bot tag

[dgw]

Description

Bot Mode spec has been ratified (ircv3/ircv3-specifications#495). Since we haven't published a release with support for this message tag yet, it's a very easy decision to take right now that we'll only support the finalized spec and not the WIP version.

Checklist

• I have read CONTRIBUTING.md
• I can and do license this contribution under the EFLv2
• No issues are reported by make qa (runs make quality and make test)
• I have tested the functionality of the things this change touches

[half-duplex]

What implements the draft version? How safe is the assumption that they'll all switch to the final spec/tag promptly? Otherwise I'm not sure there's a reason to drop the draft one.

[dgw]

The top comment of the linked IRCv3 PR is a non-exhaustive list of existing implementations that may or may not have yet switched to the final tag name. There are 8 servers/clients listed, including Sopel itself. However, since the server adds the message tag, the client implementations are irrelevant to this decision. That leaves just 3 IRCds with draft impls to consider.

Pushing to ratify the spec this week was because InspIRCd wanted to ship the feature in a release on Friday, 4/29. It's safe to assume they will use the final tag name. The other servers will almost certainly release new versions with this feature in its final state before Sopel 8.0 is done. (They all have much better release cadences than we do…)

In this specific case there are no meaningful differences between the draft and final specs, but in general it's improper to implement a WIP spec as I did in #2089, where it responds to both the prefixed and unprefixed tag names.

[half-duplex]

Fair enough. We also have +B, and that's probably all anyone should be relying on until they've got the final bot mode cap.