Reset agent.isUnderAttack only after evaluating all rules.

[tommy33790]

Closes #79

📜 Description

Changes proposed in this pull request:

• agent.isUnderAttack is no longer reset on read
• Therefore it can be used in multiple rules again

🔨 Breaking Changes

• None

✅ Checklist:

• Created tests which fail without the change (if possible)
• Extended the documentation (if necessary)
• Checked the checklist and figures that nothing on it is possible

❓ Open Questions:

• There's a slight possibility that the agent is attacked while evaluating rules. Therefore not all rules have access to the same information (in lower priority rules isUnderAttack might be true while it wasn't when evaluating high priority rules). Do we have to protect against that?

[DivineThreepwood]

good finding!