style: Apply consistent field order to CommandSetUpgrade Behavior modules

[Stubbjax]

This change applies a consistent field order to all CommandSetUpgrade Behavior modules across all INI files. Fields are ordered based on the most common order patterns and their code declaration/parse orders.

Note: The invalid modules, ModuleTag_18 and ModuleTag_19, in Demo_GLABarracks will be removed in a future change.

Order

Below is the order applied to the respective module.

Behavior CommandSetUpgrade
  CommandSet
  TriggeredBy
  ConflictsWith
  RemovesUpgrades
  FXListUpgrade
  RequiresAllTriggers
  CommandSetAlt
  TriggerAlt

[xezon]

This pull is labeled for Gen but only contains ZH edits.

[xezon]

Would have been nice if TriggeredBy, ConflictsWith, RequiresAllTriggers sat together

Although, I see it matches Code definition now.

Behavior CommandSetUpgrade
  CommandSet
  TriggeredBy <-----------
  ConflictsWith <-----------
  RemovesUpgrades
  FXListUpgrade
  RequiresAllTriggers <-----------
  CommandSetAlt
  TriggerAlt

{ "TriggeredBy",		INI::parseAsciiStringVector, nullptr, offsetof( UpgradeMuxData, m_activationUpgradeNames ) },
{ "ConflictsWith",	INI::parseAsciiStringVector, nullptr, offsetof( UpgradeMuxData, m_conflictingUpgradeNames ) },
{ "RemovesUpgrades",INI::parseAsciiStringVector, nullptr, offsetof( UpgradeMuxData, m_removalUpgradeNames ) },
{ "FXListUpgrade",	INI::parseFXList, nullptr, offsetof( UpgradeMuxData, m_fxListUpgrade ) },
{ "RequiresAllTriggers", INI::parseBool, nullptr, offsetof( UpgradeMuxData, m_requiresAllTriggers ) },

[Stubbjax]

Would have been nice if TriggeredBy, ConflictsWith, RequiresAllTriggers sat together

Although, I see it matches Code definition now.

We could reorder UpgradeMuxData? For example:

TriggeredBy
RequiresAllTriggers
ConflictsWith
RemovesUpgrades
FXListUpgrade

[xezon]

Keeping it in sync with the Code definition order also makes sense. No strong preference.