Add atomic memory block around unsafe code blocks

[antoniofilipovic]

Fixes https://github.com/memgraph/memgraph/actions/runs/7100898041/job/19359933556

Slack thread: https://memgraph.slack.com/archives/CS5827FK3/p1702652195334839?thread_ts=1702627200.164709&cid=CS5827FK3

If idea seems good, I will apply this to rest of operations in vertex_accessor and edge_accessor which from memory allocation should be "atomic".

[master < Task] PR

• Check, and update documentation if necessary
• Provide the full content or a guide for the final git message

To keep docs changelog up to date, one more thing to do:

• Write a release note here, including added/changed clauses
• Tag someone from docs team in the comments

[as51340]

I don't understand why we need DoCheck?

[as51340]

💪

[Ignition]

Rather than block one kind of exception, why not make the code exception safe? e.g. if SetProperty has memory exception then need to unlink and delete delta inside a catch + rethrow

[antoniofilipovic]

Rather than block one kind of exception, why not make the code exception safe? e.g. if SetProperty has memory exception then need to unlink and delete delta inside a catch + rethrow

@Ignition I would say it would make code even more dependent on OOM Exception checks. If I understood correctly, in that case I would need to have Try Catch blocks inside the SetProperty function in VertexAccessor, which means that an exception would be thrown, we will have stack unwinding there and afterward we need to process exception and do additional steps to revert changes. This way it is in my opinion more performant and "cleaner" to have Atomic memory block, which doesn't allow to throw exception, and it is more reusable also. There is no exception thrown until needed.

[Ignition]

For we need now, this works.
One small change requested.