[New Feature] Trigger information extraction

[Rampastring]

First Check

• [X] I added a very descriptive title to this issue.
• [X] I used the GitHub search to find a similar issue and didn't find it.
• [X] I have attached as much information as possible (screenshots, videos, links, etc).

Description

While triggers work properly most of the time, as a mapper/scripter you can sometimes run into issues where, for example, a win condition refuses to work in a custom mission. When this happens, it becomes a painful case of trial-and-error where you adjust the trigger(s), test the mission again, then adjust again, re-test the mission and so on until it works. This takes considerable time, especially because you're doing it blind; the game doesn't give any ideas or pointers to what is going on with the triggers.

A tool for extracting trigger data from the game to a log file would be useful. It could act as a developer-mode keyboard command which, when pressed, would dump out data such as each trigger's ID, their state (whether it has sprung, or whether it's destroyed), which event in their event list they are currently waiting to occur, and the enabled/disabled states of all local variables. The mapper could then check this log to see which part of their trigger conditions aren't working properly.

Proposed Code (optional)

No response

Additional Context

No response