[BugFix] [C++] Make examples to generate result files under build type of release

[lixueclaire]

Proposed changes

As titled.

Types of changes

What types of changes does your code introduce to GraphAr?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have signed the CLA
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

Fix issue #172

[github-actions]

🎊 PR Preview 0654497 has been successfully built and deployed to https://alibaba-graphar-build-pr-173.surge.sh

_{🤖 By surge-preview}

[acezen]

Could you help to unify the similar ASSERT and ABORT in unit tests as well?

[lixueclaire]

Thank you for the reminder. Currently, assert is only used in the examples.

[acezen]

LGTM