improve memtracker, add missed check & remove unnecessary thenError&tryCatch check

[codesigner]

What type of PR is this?

• bug
• feature
• enhancement

What problem(s) does this PR solve?

Issue(s) number:

#5205
#5206

Description:

• When memory tracker is turned on, we should make sure if some std::bac_alloc throws, the corresponding query should be killed with correct error message. For this purpose, I test with mannually add throw std::bac_alloc to check expected bahavior happens.

• Almost every memtracker turned on code block, tested with mannually throw bad_alloc, check query failed with except error, if // MemoryTrackerVerified added to that context, these places were manually test;

• graphd:

  • some thenError is remove, which is not nessacery, future most of time can chined and returned to up callstack; (what @Shylock-Hg comment in previouse pr it right, but have no time to check every place, some place remains need thenError)
  • some code block missed turned on memtracker, added;

• storaged:

  • remove XXXProcessor::process's try catch, added the root catch in GraphStorageServiceHandler.cpp;
  • added a MemoryCheckScope to ease wrap a function in memory tracker turned on context, used by async execution submitted to executor;

• rpc

  • added memroy tracker in DataSet::read that decode DataSet from wire， every rpc response from stroage is defined as a DataSet, so I think this is enough; have tried add a throw in DataSet::read, it works as expected.

• fix a build issue when build using gcc with sanitize

How do you solve it?

Special notes for your reviewer, ex. impact of this fix, design document, etc:

Checklist:

Tests:

• Unit test(positive and negative cases)
• Function test
• Performance test
• N/A

Affects:

• Documentation affected (Please add the label if documentation needs to be modified.)
• Incompatibility (If it breaks the compatibility, please describe it and add the label.）
• If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
• Performance impacted: Consumes more CPU/Memory

Release notes:

Please confirm whether to be reflected in release notes and how to describe:

ex. Fixed the bug .....

[codecov-commenter]

Codecov Report

Base: 76.77% // Head: 78.68% // Increases project coverage by +1.90% 🎉

Coverage data is based on head (8eabe16) compared to base (ff4cb8c).
Patch coverage: 72.20% of modified lines in pull request are covered.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5199      +/-   ##
==========================================
+ Coverage   76.77%   78.68%   +1.90%     
==========================================
  Files        1109     1110       +1     
  Lines       82965    82950      -15     
==========================================
+ Hits        63694    65266    +1572     
+ Misses      19271    17684    -1587     

Impacted Files	Coverage Δ
src/clients/meta/MetaClient.h	92.30% <ø> (ø)
src/codec/RowReaderWrapper.cpp	79.38% <ø> (+1.60%)	⬆️
src/codec/RowWriterV2.cpp	84.90% <0.00%> (+0.64%)	⬆️
src/common/base/Arena.cpp	95.00% <0.00%> (+4.52%)	⬆️
src/common/base/Status.cpp	57.83% <0.00%> (-2.17%)	⬇️
src/common/base/Status.h	89.09% <0.00%> (-3.37%)	⬇️
src/common/datatypes/Value.cpp	75.07% <0.00%> (+0.66%)	⬆️
src/common/datatypes/ValueOps-inl.h	61.09% <ø> (+0.18%)	⬆️
src/common/expression/ArithmeticExpression.cpp	91.66% <0.00%> (+3.66%)	⬆️
src/common/expression/Expression.cpp	52.94% <0.00%> (+0.46%)	⬆️
... and 345 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[yixinglu]

do you forget to restore these tests?

[codesigner]

do you forget to restore these tests?

Yes, good catch