Fix transactionality for direct & indirect container default triples

[no-reply]

DirectContainer#create and IndirectContainer#create both require multiple transactions in cases where they automatically add default triples membership and/or inserted content relation triples.

We should resolve this so the behavior is consistently transactional and skewed reads are impossible; this is complicated by variable read isolation semantics for transactions.

See the documentation for DirectContainer#create.