Add a defining for AutoDeath on whether it can trigger when in Limbo state or as a passenger

[DeathFishAtEase]

https://www.phoboscn.top/t/topic/609

A unit designed with AutoDeath.OnOwnerChange, when serving as a passenger of a transport with OpenTopped=true, happens to need Passengers.SyncOwner to sync the passenger's owner change to prevent them from continuing to attack the transport's new owner, but they do not want this handling to trigger the passenger's self-destruction.

• AutoDeath.AllowLimboed can be used to define whether AutoDeath is triggered when the unit is in limbo state.
• AutoDeath.AllowPassenger can be used to define whether the unit triggers AutoDeath when it is a passenger.

In rulesmd.ini:

[SOMETECHNO]                                   ; TechnoType
AutoDeath.AllowLimboed=true                    ; boolean
AutoDeath.AllowPassenger=true                  ; boolean

Here, the logic has been simplified at the INI writing level:
- Passengers only check their own `AutoDeath.AllowPassenger` and do not check `AutoDeath.AllowLimboed`, regardless of what the `OpenTopped` of the transport they are riding is.

[phoboscn-bot]

To Chinese users:
This pull request has been mentioned on Phobos CN. There might be relevant details there:

致中文用户：
此拉取请求已在 Phobos CN 上被提及。那里可能有相关详细信息：

https://www.phoboscn.top/t/topic/647/1

[github-actions]

Nightly build for this pull request:

• compiled-dll-58a6405bf2062ee843634d0e2d71ce45e57f105c.zip
  These artifacts will expire in 90 days and will not be available for download after that time.

This comment is automatic and is meant to allow guests to get latest nightly builds for this pull request without registering. It is updated on every successful build.

[DeathFishAtEase]

After more exploration, it was found that the original handling's support for objects in Limbo state was not complete (I previously thought #830 had handled this part, but it was actually support for LimboDelivery) and this leads to the fact that even if the implementation is completed, the two flags cannot be set to true by default, otherwise it will break existing behavior; this PR is shelved for now.

[DeathFishAtEase]

In any case, supporting Limbo scenarios for more AutoDeath conditions is something that should have been done but has not been completed. This PR effectively fulfills the corresponding feature request, and passengers inside OpenTopped=true transports are also not affected by the original defects. This PR only provides the toggle statements; how the toggles should behave when on or off should be addressed outside of this PR.

[DeathFishAtEase]

Tested by: https://www.phoboscn.top/t/topic/647/4?u=noble_fish

[DRON]
AutoDeath.Behavior=kill
AutoDeath.AfterDelay=200
AutoDeath.AllowLimboed=no

[SQD]
AutoDeath.Behavior=kill
AutoDeath.AfterDelay=200
AutoDeath.AllowLimboed=no

[E1]
AutoDeath.Behavior=kill
AutoDeath.OnOwnerChange=yes
AutoDeath.AllowLimboed=no
AutoDeath.AllowPassenger=no

[BFRT]
InitialPayload.Types=E1
InitialPayload.Nums=5
Passengers.SyncOwner=yes

[TaranDahl]

Should comment specific design rationale

[TaranDahl]

Should check if AutoDeath can still work when technos are in non-opentopped vehicles before merging.
Also, the comment issue mentioned above should be addressed.

[Coronia]

not sure if this should be removed as it'll still execute the line and set ShouldBeDead to true, which might make it die after leaving the transport