Handle analytical mode in community_detection during parallel changes

[Darych]

Description

NB: PR taken over by @antepusic; connected with memgraph/memgraph#1395

Since there are no ACID guarantees in analytical storage mode, the graph may get modified by parallel transactions while the user’s query is running. Query procedures and functions that return graph elements (nodes and relationships) should be robust to the deletion of graph elements, and this PR aims to fix that.

This PR contains changes to query modules that ensure the intended behavior:

• Query modules written with the C and C++ APIs check the existence of values that may contain graph elements before returning them (Python API query modules do this under the hood)

Merge commit message:

Add proper handling of deleted return values for query procedures and functions ran in analytical mode

Pull request type

• Bugfix

Related issues

Resolves memgraph/memgraph#1036 (together with memgraph/memgraph#1395)

######################################

Reviewer checklist (the reviewer checks this part)

Module/Algorithm

• Core algorithm/module implementation
• Query module implementation
• Unit tests
• End-to-end tests
• Code documentation
• README short description
• Documentation on memgraph/docs
• Update GQLALchemy signatures in query builder using query module signature generator

######################################

[as51340]

I think good job in general, take care about duplication please :)

[as51340]

And you have build errors, please take care about that before requesting review again. For next time tip: it is better to request review after build errors are fixed since it gives reviewer more confidence that hey this is good and meaningful fix without negative impact on the rest of the system

[Darych]

My initial idea was to make body of GetInnerNodeIdOpt a default implementation for GetInnerNodeId, so we will have just one implementation. I mentioned about this HERE
Currently. we have 2 implementations and users should think which one they need to use in their modules.
@antoniofilipovic what do you think?

[Darych]

LGTM. I can't approve the PR since I'm author.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.7% Duplication

[antepusic]

@vpavicic As this PR is the MAGE side of memgraph/memgraph#1395, they are covered by the same docs PR (memgraph/documentation#361) and should both be linked in the same release note.