perf: smarter transactions and authorization for built-in actions

[davenewza]

Performance improvements on built-in actions

Summary:

• create: reduced from 5 to 2 - 5 db hits
• update: reduced from 6 to 2 - 4 db hits
• delete: reduced from 6 to 2 - 4 db hits

Smarter authorization

For all action types, we perform better early authorization checks, which means we can avoid unnecessary database hits when row-based permissions aren't being used. For create, we even avoid the use of transactions entirely.

Typically, this is the order of database events (i.e. incurring a DB 'hit') for an built-in create action:
a) open transaction
b) execute create statement
c) perform row-based permissions query
d) commit (or rollback) transaction

That is FOUR hits to the database, which is expensive especially when no row-based permissions are even performed.

Now we check if transaction and row-based permission checks are even needed. If they aren't needed, then the action will be reduced to a single query - executing the insert statement without a transaction block

No more transactions on update and delete

Furthermore, transactions were only in place on update and delete as a fail safe if multiple rows happened to be affected (which would be an error on Keel's part). We have so many tests and I think the risk of this happening is so low. The cost of a transaction for every single action call is quite high, so I've opted for dropping it.