revisions for CRUD operations with $full

[freekrai]

Description

This PR addresses the fact that when no user is set in flows aka system or $full permissions operations, then the app didn't store revisions to track the changes.

Originally, it set the customAccountability to null, now it will set it as follows:

customAccountability = {
  user: null,
  role: null,
  admin: true,
  app: true,
  ip: '',
  userAgent: '',
  origin: '',
  share: undefined,
  share_scope: undefined,
  permissions: [],
};

This leads to revisions being created by the flow so we can track the changes.

Addresses #15345, fixes #15346

Type of Change

• Bugfix
• Improvement
• New Feature
• Refactor / codestyle updates
• Other, please describe:

Requirements Checklist

• New / updated tests are included
• All tests are passing locally
• Performed a self-review of the submitted code

If adding a new feature:

• Documentation was added/updated

[licitdev]

Thank you for the PR. It works well for the item update operation. 👍

This change should be propagated to all operations that has permissions === '$full'. Let's also extract the customAccountability conditional code-block into a util such as getOperationCustomAccountability. 🙂

[freekrai]

Right will push an update shortly

[freekrai]

@licitdev I've moved the codeblock into getAccountabilityForRole as a system role, and updated create, update read, and delete to use it.

So that calling:

customAccountability = await getAccountabilityForRole('system', { database, schema, accountability });

returns the block I had above, this lets it work the same as public, trigger or anything else.

[licitdev]

LGTM! 👍