Asynchonous methods to not have Async suffix

[StephenHodgson]

Describe the bug

Asynchonous methods do not properly conform to the industry standard naming conventions for Task-based Async Pattern (TAP), which stipulate to add Async suffix to the name of the methods to clearly show that they are awaitable.

Asynchronous methods in TAP include the Async suffix after the operation name for methods that return awaitable types, such as Task, Task<TResult>, ValueTask, and ValueTask<TResult>.

[StephenHodgson]

Should be simple enough to add Async overload without introducing breaking changes.

[atteneder]

I don't disagree, but such changes bring the danger of breaking the API.

There's also no technical benefit, so this will be a low priority.