Elide async lambda and use WrappedCallbackAsync directly

[HenKun]

Fixes #12697

Proposed changes

• Elides the async lambda in two locations and uses the method group directly

Customer Impact

• Depending on the rate InvokeAsync is called to update the UI, it can result in a performance improvement
• Due to avoiding creating a new delegate each time and creating a state machine, memory can be saved and the GC pressure be reduced

Regression?

• No

Risk

• Propagation of exceptions from within callback. But since WrappedCallbackAsync wraps callback in a try-catch block this should be save and not change the current behavior.

Test methodology

• Code review of related code
• Existing tests should still pass

Microsoft Reviewers: Open in CodeFlow