Conform to C.128, aka: Virtual functions should specify exactly one of virtual, override, or final

[fluffyfreak]

C.128: Virtual functions should specify exactly one of virtual, override, or final
I found out that there's an isocpp standard for this and decided that I'd see how much work it'd be to make us compliant with this and maybe shake out some bugs.

No issues found is the good news and after a LOT of edited files I don't think there's any cases of virtual, override, and/or final appearing in the same function declaration 👍

Sadly this does touch on a LOT of files.

[sturnclaw]

I really appreciate moving to significantly less keyword noise, but this rebase does indeeed touche a number of files - and will likely cause a bunch of merge conflicts for open PRs. In that light, I'd like to merge this significantly closer to the upcoming release as a "cleanup task" once the major feature branches are done being merged.

[sturnclaw]

Hi @ollobrains - I appreciate the desire to help, but I'd ask you to refrain from pasting AI-generated responses. Unfortunately, though it may look useful on paper, the only thing that the AI is doing is summarizing existing work that's already been done in the pull request and proposing it as though it needs to be done again.