style: Apply consistent field order to FireWeaponWhenDeadBehavior Behavior modules

[Stubbjax]

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

Order

Below is the order applied to the respective module.

Behavior FireWeaponWhenDeadBehavior
  RequiredStatus
  ExemptStatus
  DeathWeapon
  StartsActive
  TriggeredBy
  RequiresAllTriggers
  ConflictsWith
  RemovesUpgrades
  FXListUpgrade
  DeathTypes
  VeterancyLevels

[xezon]

It is a bit unfortunate that the ExemptStatus and RequiredStatus are not consistently ordered:

Behavior FireWeaponWhenDeadBehavior
  RequiredStatus <----------
  ExemptStatus <----------
  DeathWeapon
  StartsActive
  TriggeredBy
  RequiresAllTriggers
  ConflictsWith
  RemovesUpgrades
  FXListUpgrade
  DeathTypes
  VeterancyLevels

Behavior EjectPilotDie
  DeathTypes
  VeterancyLevels
  GroundCreationList
  AirCreationList
  ExemptStatus <----------
  RequiredStatus <----------
  InvulnerableTime

[xezon]

Would have been nice if DeathTypes and DeathWeapon sat together

Behavior FireWeaponWhenDeadBehavior
  RequiredStatus
  ExemptStatus
  DeathWeapon <--------
  StartsActive
  TriggeredBy
  RequiresAllTriggers
  ConflictsWith
  RemovesUpgrades
  FXListUpgrade
  DeathTypes <--------
  VeterancyLevels

[Stubbjax]

It is a bit unfortunate that the ExemptStatus and RequiredStatus are not consistently ordered:

I tend to agree, though I was primarily attempting to align them using the existing patterns within their own modules. I can apply the DieMuxData format to each individual module/PR or I can do a single follow-up standardisation?

DeathTypes
VeterancyLevels
ExemptStatus
RequiredStatus

[xezon]

Up to you