Audit docs (mostly) for incorrect use of the term "module"

[dgw]

Description

This is the final step for 7.1 in #1738. Making these commits was literally just me going through about 1,400 find-in-files results for the string "module". Fortunately I was able to skip a lot with negative regex lookarounds (e.g. decorators, object attributes).

I mixed in a few little tweaks to other stuff, because without them it would have been a very small PR indeed.

In summary:

• coretasks: audit for outdated uses of "module" vs. "plugin" (6fa4bb1)
• irc: audit for outdated use of "module" vs. "plugin" (650e672)
  • Some of this actually changes an argument name, something we might not want to do right now (and in fact the "module" moniker goes all the way down into the CapReq type from irc.utils).
  • More importantly, it seems that nothing actually uses the cap_req() function provided here. Something to address in a future patch, perhaps.
• irc.utils: fix docs for CapReq param prefix (f8ed9e5)
  • The empty string is also allowed; it means "request this if no other CapReq forbids it".
  • Here I did not change the parameter name module or anything else, yet. I'm still not entirely sure how this and cap_req() fit together, and we'll probably end up dropping most or all of the above commit.
• logger: decorate get_logger() with deprecation info (e02a286)
  • I think this was deprecated before we added that warning_in parameter for tools.deprecated() in tools: add warning_in arg to @deprecated; deprecate get_input #1872, but now we won't have to remember to decorate this function later.
• plugins: audit docs for outdated use of "module" vs. "plugin" (d5854f8)
• plugins.handlers: small fixes (all uses of "module" are correct) (850a178)
• irc.utils: rename "module" param & attribute to "plugin" (33b094b)
  • Kept CapReq.module as a @tools.deprecated @property. Looks like nothing was accessing it, but let's still keep it around until 8.0 just in case.

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
  • Note: There are minimal code changes (none if the single code-touching commit to irc is rejected)

Notes

Yes, I'm aware that I threw some unrelated stuff in here, not that long after admonishing @Exirel for doing the same in #1944. I don't regret it. That stuff needs fixing, too. 😜

[Exirel]

👍

[dgw]

@Exirel You still OK with this, including the new commit I just added (33b094b)? The "deprecated property" solution was super obvious but I was so distracted by other stuff when putting together the rest of this PR that I didn't think of it. 😅

[Exirel]

You still OK with this, including the new commit I just added

Yes, all good to me!