AutoDeath based on player power status and player credits

[Flactine]

Add new auto-death conditions based on the owner's power status and credits.

• PlayerPowerState: The object will die if its owner's power status matches the configured state.
  • low / consumer: Trigger when the owner is in low power.
  • full / normal: Trigger when the owner is not in low power.
• PlayerMoney.Max / PlayerMoney.Min: The object will die based on the owner's available credits.
  • If only PlayerMoney.Max is set, triggers when money is not above this value.
  • If only PlayerMoney.Min is set, triggers when money is not below this value.
  • If both are set, triggers when money is inside the range.

---

• PlayerPowerState：当对象所属方的电力状态符合设定条件时，则对象死亡。
  • low / consumer：当对象所属方处于电力不足状态时触发。
  • full / normal：当对象所属方未处于电力不足状态时触发。
• PlayerMoney.Max ／ PlayerMoney.Min：根据对象所属方的资金决定对象是否死亡。
  • 仅设置 PlayerMoney.Max 时，当资金不高于该值时触发。
  • 仅设置 PlayerMoney.Min 时，当资金不低于该值时触发。
  • 同时设置时，资金处于区间内时触发。

In rulesmd.ini:

[SOMETECHNO]                         ; TechnoType
AutoDeath.PlayerPowerState=none     ; enumeration (none | low/consumer | full/normal)
AutoDeath.PlayerMoney.Max=-1         ; integer
AutoDeath.PlayerMoney.Min=-1         ; integer

[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/603/1

[github-actions]

Nightly build for this pull request:

• compiled-dll-f0c619ace2459b99c59aa8207c3705dc5c45b580.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.

[TaranDahl]

Note: You can use AI skill for generating Chinese docs.

[Coronia]

would be better to rename the tag to none/low/full since it's been widely used in many places already

[Coronia]

for code style and reusablity, some tag/variable names should be changed, especially PowerStatus which already has common terminologies and is likely to be reused in the future

[DeathFishAtEase]

@Coronia I think the content of Request changes has been satisfied; it is enough to resolve conflicts and let testers test again. (The latest test post under the corresponding forum topic was compiled by the user themselves because no new Nightly Build was generated, rather than being generated by the workflow.)