CfgPatches sorting

[commy2]

This is inspired by A3_Data_F_XXX_Loadorder and restores what cba_main(_a3) once did.

In vanilla every bigger update X (e.g. Orange, Tanks) works like this:

A3_Data_F_X
    requiredAddons: A3_Data_F_(X-1)_Loadorder

A3_feature1_F_X
    requiredAddons: A3_Data_F_X
A3_feature2_F_X
    requiredAddons: A3_Data_F_X
A3_feature3_F_X
    requiredAddons: A3_Data_F_X

A3_Data_F_X_Loadorder
    requiredAddons: A3_feature1_F_X + A3_feature2_F_X + A3_feature3_F_X

Where (X-1) is the last big update before X.

This ensures that the config patches of big updates are loaded in chunks (everything update 1 first, then everything update 2, etc.), which makes the master config predictable and setting up requiredAddons easier.
It is similar of how CBA is supposed to work (we did it first!), but our A3_Data_F_X is named cba_common and our A3_Data_F_X_Loadorder cba_main.
Problem is that over the years this wasn't maintained properly (partly due to _Loadorder not being a thing for years), so many cba patches use vanilla game patches as required addons instead of just cba_common, cba_main not properly waiting for every cba patch, and some weird almost circular dependencies.

With this pull request cba_common now requires the latest big update of Arma 3 (A3_Data_F_Tanks_Loadorder) and cba_main/cba_main_a3 waits for every config patch from cba (bar optionals but w/e).
I also put every config patch into one config.cpp file, and some of these inside sub-folders of the PBO folders. I think this is cleaner, but if someone has a problem with that I can revert it for this pull request.

Note that ace_main works differently than cba_main.
ace_main is responsible for waiting for every base game patch and then ace_common requires ace_main. Which makes ace_main kind of redundant in this regard but w/e.
ace_main is always the first config loaded of the mod instead of the last.
An addon like A3_Data_F_X_Loadorder doesn't make much sense for x = ACE, because of the modular nature of ACE3.

Every addon X relying on CBA can now just safely use cba_main (or cba_main_a3) as requiredAddon in their x_common equivalent.
The names cba_common and cba_main are not very descriptive, which is regretable and something I'll hopefully fix for A4 (bwc)!

'

A list of all config patches created by cba can be generated by using:

private _cbaFolderName = configSourceMod (configFile/"CfgPatches"/"cba_main");
"true" configClasses configFile/"CfgPatches" select {configSourceMod _x isEqualTo _cbaFolderName} apply {toLower configName _x}

assuming that the addons folder is placed inside a folder named "cba".

After this PR, the addons are loaded in this order:

cba_common, cba_events, cba_hashes, cba_jr_prep, cba_keybinding,
cba_modules, cba_music, cba_network, cba_settings, cba_statemachine,
cba_strings, cba_vectors, cba_xeh, CBA_Extended_EventHandlers, cba_ee,
Extended_EventHandlers, cba_xeh_a3, cba_accessory, MRT_AccFncs, cba_ai,
cba_arrays, cba_diagnostic, cba_help, cba_jr, asdg_jointmuzzles,
asdg_jointrails, cba_ui, cba_ui_helper, cba_versioning, cba_main,
cba_main_a3