Improve API for tracking delayed execution at runtime.

[sovdeeth]

Description

The current method of checking if the current execution has been delayed utilises Delay.isDelayed(Event), which returns whether a delay has been run in that event before. If the event only corresponds to a single trigger, this is ok. However, as soon as 2 triggers enter the picture, problems arise:

on jump:
  send isDelayed # sends false
  wait 1 tick # adds to DELAYED
  send isDelayed # sends true

on jump:
  send isDelayed # uh oh, this ran after the first event, so the event's already in DELAYED! returns TRUE
  wait 1 tick
  send isDelayed # sends true

This PR attempts to resolve that by moving this logic to Trigger, so each trigger tracks whether it has been delayed for an Event or not. The old methods are deprecated and marked for removal, but are still functional.

Current issues/concerns:

• Grabbing a Trigger from an Expression context
• Is getTrigger reliable when working with sections that completely overwrite context, like EffSecSpawn?

Some simple cleanup was done to classes affected by the deprecation. Anything more is out of scope.

---

Target Minecraft Versions: any
Requirements: none
Related Issues: #7393 (not a fix)

This is not in a state for approval; it does not even build.

[sovdeeth]

I cannot think of a way to figure out the current triggeritem from an Expression, or to even reliably find it and store it at parse time, so this is on hold until a better runtime context (with execution stack!) is implemented.