Add context to triggers/automations

[ogenstad]

The focus of this PR is to get the automation triggers from Prefect working again in the develop branch. This is done by ensuring that we send the now required InfrahubContext object in different formats depending on if it's a trigger setup within Prefect (then we send it as JSON payload from the event.payload['context'] data and convert it into a dictionary instead of sending it as a string. The alternative is when se just submit or execute a workflow and send the context object as is.

The InfrahubContext object has been added as a required object to the event Metadata field. There are a few things to note about this:

• With this in place some of the existing data in the metadata object such as account and branch are redundant. I didn't want to change to much within a single PR but before 1.2 is released we should phase out the old fields
• As the AccountSession is required for the InfrahubContext I've added that information where applicable (with some dummy data within the tests). However we also have it in git/integrator.py where we don't yet have access to the context object. As things weren't working right now with the triggers I added some dummy data in that specific location as well. There I think we need to start from the beginning and see where we can create a proper AccountSession object and send it from the originating task (the other option would be to make the AccountSession optional but I think we can use it pretty much everywhere)

Because we always want to send the InfrahubContext as part of the event payload I added a new .get_event_payload() method that should only be defined on the root InfrahubEvent object and then child classes can override the get_payload() method without having to worry about the requirement to include the "context" key.

I added a new test to infrahub_docker where we validate that the trigger for the computed attribute (for Jinja) is working. So now we at least won't run into the same situation again. Those tests should be expanded on upcoming PRs though to also run the same type of tests for the Python Transform based computed attributes as well as testing the computed attributes on different branches.

I also enabled a test that was previously disabled. I'm not sure why it was failing before or if it started to work after the recent changes to the InfrahubEvent GraphQL query.

[codspeed-hq]

CodSpeed Performance Report

Merging #5758 will not alter performance

_{Comparing pog-add-context-to-triggers-IFC-1244 (dbf932b) with develop (81a514f)}

Summary

✅ 11 untouched benchmarks