[Story] Smart Triggers from file/resource

[andrewazores]

Another avenue for users to define smart triggers would be some configuration file(s) loaded at Agent startup. The file contents would use the same syntax as the agentmain string arguments, but perhaps could be either comma-separated or newline-separated. The Agent could look for such a configuration file as a classpath resource with a default name, or perhaps there could also be a configuration option like cryostat.agent.smart-trigger.config-files that defines a list of filesystem paths that should be read and parsed, or both, etc.

[andrewazores]

This would end up tying in similarly to the various Declarative configurations being implemented in the Operator and Helm Chart right now, and would also be useful for the Operator's Autoconfiguration feature. The user could use the Operator to specify a ConfigMap name, for example, and the Operator would mount that ConfigMap as a volume to the target application, where the Agent would then pick up the Smart Triggers contained within the ConfigMap and load them.