Better tests and more corner cases for chunk deletion of containers
From discussion in https://gitlab.com/caosdb/caosdb-pylib/-/merge_requests/61?view=parallel#note_622538627:
I think we should have (possibly, integration tests) for the following cases:
- One deletion of a large container of weakly connected records that will cause a too long URI, and will fail with "stupid" chunking (i.e., Record chunk_size + 1 references Record 1) (Will fail with dev, but probably not with current implementation of this branch)
- Same thing but now with RecordTypes and Properties included (May still fail in the current state of this branch, fix is WIP)
- Perhaps more corner-cases of dependencies?
- One with too many dependencies. Should this really be caught by the client or should it be sent to the server in any case? In the former case, the correct raising of an error could be unit-tested, in the latter case, this will be an xfailing integration test.
Some of these may still fail, because ultimately, they cannot be fixed without fixing the too long URIs, so they will have to be set to xfail.
Also consider Files and States as additional corner cases.