feat: add EntityEdgeDeletionAuthorizationInferenceBehavior for canViewerDeleteAsync

[wschurman]

Why

This PR adds a new concept for optimized evaluation of canViewerDeleteAsync: EntityEdgeDeletionAuthorizationInferenceBehavior.

The way it works is: when the method goes to recursively authorize all cascading deletes/set-nulls for an entity being checked in canViewerDeleteAsync, an application developer can specify that checking one instance of an edge of an association type is sufficient for inferring that all edges share the same privacy checks and loading all of them isn't necessary. Without this, all edges are loaded and authorization to cascade delete / set null are checked individually.

This is more of a best-effort optimistic evaluation to tell ahead of time whether a deletion will succeed or fail, and is not used during actual deletion since an application developer may apply it incorrectly.

It was inspired by this comment: #224 (review)

How

Add concept with explanation in comments, add tests.

Test Plan

Run tests.

[wschurman]

• feat: add EntityEdgeDeletionAuthorizationInferenceBehavior for canViewerDeleteAsync #243 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @wschurman and the rest of your teammates on Graphite

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (15117fc) to head (7954f53).

❗ Current head 7954f53 differs from pull request most recent head 265b641

Please upload reports for the commit 265b641 to get more accurate results.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #243   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           72        72           
  Lines         1949      1970   +21     
  Branches       267       278   +11     
=========================================
+ Hits          1949      1970   +21     

Flag	Coverage Δ
integration	100.00% <100.00%> (ø)
unittest	100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[wschurman]

One concept I'd like to be able to express alongside this (that I haven't figured out yet) is the ability to ensure canViewerDeleteAsync doesn't load too many entities unexpectedly due to a forgotten edgeDeletionAuthorizationInferenceBehavior specification somewhere in the cascade tree.

Put another way, the most common use of this will likely be doing a simple optimistic check ahead of long-running bulk/batch deletion of a tree of entities. It'd be nice to be able to limit how many entities can be loaded in that execution of canViewerDeleteAsync to prevent OOM.