Consider updated fields for Jinja2 based computed attributes

[ogenstad]

Changes in this PR

• The computed attribute mutation didn't manage the update in a transaction so I've wrapped the save() method within a new transaction
• Changed the node mutated event to include a "fields" key in the payload (due to this I also had to modify the webhook as it gained an extra level of "indentation", we'll probably refactor the webhook completely in a not to distant future regardless)
• Use these updated fields as part of the lookup to find computed attributes in the schema. The goal is to only run the computed attribute calculation if a relevant attribute/relationship has been updated.

Note in this iteration I've only isolated the change to when we are actually running the Computed Attributes, it will save us from querying the backend with the SDK when we know that it isn't strictly required.

I view this as an initial step to improve the performance a bit. The next iteration of this would be to modify the event automations so that the triggers themselves have these fields built in. I think it would be nice to refactor the automations in general as we'll end up with potentially quite a few additional automations when this is in place. Most of the code for this was already in place since before we started using it as automations in Prefect but the filtering was ignored as we always sent in an empty list for "updated_fields".

Also I really dislike that I did with the "update_fields" parameter and the use of ujson, we have this with the webhooks too. Would like a cleaner solution.

Final note: To improve things in a similar way for the Transforms I think we really have to spend time to rewrite and enhance the GraphQLQueryAnalyzer.

[codspeed-hq]

CodSpeed Performance Report

Merging #5307 will not alter performance

_{Comparing pog-computed-attribute-jinja-updated-fields (4942eb7) with release-1.1 (530fb03)}

Summary

✅ 10 untouched benchmarks

[ajtmccarty]

not sure if this matters here, but I have encountered problems where changes are not written to the database until the transaction is closed and that prevents us from getting the latest changes.
so maybe this to_graphql should be outside of the transaction

[ogenstad]

Ok! I moved this part out of the transaction.