versionCheck: use `allAddonsInfo` , log filePatching usages, use VAR and FUNC macros

[Fusselwurm]

• use https://community.bistudio.com/wiki/allAddonsInfo (will be released with arma3-1.1002.00)
• use GVAR & FUNC family of macros
• log clients that use filePatching (is that even possible in MP?)
• put stuff into functions

TODO:

• prettify mod names. https://gist.github.com/Fusselwurm/0f45053b0d1d3c064d2d0a340f84b30a
• uhm can we re-use pbo witelist? https://gist.github.com/Fusselwurm/b34d26bf8fc1af32b4d2849a00af9b1d ( we could of course shit on ACE version check and have only our own, convert the list and it'd be ok)

example rpt output:

21:15:22 [GRAD] (versionCheck) INFO: Client Fusselwurm version mismatch: addon core\, server version 1.2.slash3, client version 129618
21:15:22 [GRAD] (versionCheck) INFO: Client Fusselwurm is missing addons: ["x\zen\addons\dfdiews\","core\\"]
21:15:22 [GRAD] (versionCheck) INFO: version check done.

[Fusselwurm]

okay this sucks.

• for one, allAddonsInfo returns the complete (virtual) path which would be ok, but every mod does it differently and its mostly far uglier than the value derived from cfgpatches
• second, the version numbers are horrible too. for CBA-based mods at least it looks to be the git hash, for others it's a revision, yet others still use a date (wtf?) - yet never we see some major.minor.patch number

[McDiod]

Is this dead then?

[Fusselwurm]

Is this dead then?

yeah. stupid me shouldve done the other refactorings in a separate PR from the start 😒