cppcheck lints - change a lot of method params to use const ref, etc etc

[Architector4]

Ran cppcheck on the codebase and cleaned up most lints that it outputs.

The specific invocation I used:

cppcheck --project=compile_commands.json --file-filter=Source/* --check-level=exhaustive --enable=performance,information,missingInclude --suppress=missingIncludeSystem

(copy compile_commands.json from build dir to root of the project first of course)

Also includes some error handling fixups in AudioMan, some grammar fixes, and whatnot else Code Improvement™

bub fix 👍

[HeliumAnt]

Mostly fine, just make it consistent. (Move semantics would technically be more universal, however that's only if the caller uses them and there's literally nothing in the project that would do that correctly)

[Architector4]

Mostly fine, just make it consistent. (Move semantics would technically be more universal, however that's only if the caller uses them and there's literally nothing in the project that would do that correctly)

I intentionally left/put pass-by-value & move code instead of const ref at these spots.

A const ref there would unavoidably cause a clone/reallocation anyway, since those are all assignments or lead to mutation, (like module ID lookup lowercasing the string).

Move semantics in these spots at least allow for possibility of avoiding a clone altogether, but aren't worse at all than const ref if the caller forgets to use move, except in visual inconsistency you pointed out.

For cases like this, I wonder if there's a compiler lint or a static analyzer which would highlight all the missed opportunities for moves. Then it'll all be truly optimal lol

[Architector4]

For the record, I have to go sleep now; I'll fix the constness violation and whatnot else tomorrow lol

...at least the violation is not a very big deal since multiplayer is dead code anyway :v

[HeliumAnt]

gonna say ok on the move, just one small thing in the zipped modules.

Fixed the zippedModule

[Architector4]

meson update moment :D