Maintain Referential Integrity while Deleting Resources

[alexanderkiel]

Closes: #543

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (e422887) 95.84% compared to head (a63a013) 95.85%.
Report is 1 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #1425   +/-   ##
========================================
  Coverage    95.84%   95.85%           
========================================
  Files          245      245           
  Lines        15839    15874   +35     
  Branches       335      335           
========================================
+ Hits         15181    15216   +35     
  Misses         323      323           
  Partials       335      335           

Files	Coverage Δ
modules/db/src/blaze/db/api.clj	94.78% <100.00%> (+0.04%)	⬆️
modules/db/src/blaze/db/impl/batch_db.clj	94.96% <100.00%> (+0.43%)	⬆️
modules/db/src/blaze/db/impl/db.clj	97.36% <100.00%> (+0.07%)	⬆️
...les/db/src/blaze/db/impl/index/resource_handle.clj	95.08% <100.00%> (+0.25%)	⬆️
modules/db/src/blaze/db/node/transaction.clj	100.00% <100.00%> (ø)
modules/db/src/blaze/db/node/tx_indexer/verify.clj	100.00% <100.00%> (ø)
modules/db/src/blaze/db/search_param_registry.clj	97.27% <100.00%> (ø)
...dules/rest-api/src/blaze/rest_api/capabilities.clj	97.56% <100.00%> (ø)

[alexanderkiel]

Please also fill out the documentation on the delete transaction command in docs/implementation/database.md. Also please write a section on the delete interaction in docs/api.md were we say that referential integrity is checked depending on ENFORCE_REFERENTIAL_INTEGRITY since version 0.24.0.