precompiled trigger support

[niallroche]

A suggested improvement to the performance of TemplateArchiveProcessor is to add a separate compile step. While each trigger requires compilation of involving agreement-specific data, there is additional overhead in doing this every time the agreement is triggered. With this suggested logic added the trigger call can optionally skip the precompile step in cases where the code has not changed and has already been compiled. The output of the compilation could be stored for later use and passed as a param when triggering. This could give some flexibility around when the compile happens always at runtime, or if it can be done once on first trigger and then cached, or if this could be done on agreement creation, or possibly at some later APAP event such as an agreement has been signed.

[NikhilSingh1610]

Proposal:
Add an optional precompile and caching step to TemplateArchiveProcessor to avoid recompiling TypeScript on every trigger/init.

Benefit:
Improves performance by reusing compiled JS when logic hasn’t changed, while keeping current behavior as default.

Summary:
Adds compile() method for one-time compilation
trigger() and init() can use cached code
Reduces runtime overhead for repeated triggers

please assign this issue to me i would like to work on this