Fix lambda capture bug in GraphStorageLocalServer

[yixinglu]

This will crash the daemon

What type of PR is this?

• bug
• feature
• enhancement

What problem(s) does this PR solve?

Issue(s) number:

Description:

The request object in lambda function is captured by reference, this will crash the server when this async interface finishes to run and the task in threadManager haven't be executed.

How do you solve it?

Captured by copy.

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 .....

[SuperYoko]

If request won't cost too much,capture by value is better.
I'm okay with this fix, thanks.