Allow toService to be bound to async service

[AGrzes]

Description

toService method:

 public toService(service: string | symbol | interfaces.Newable<T> | interfaces.Abstract<T>): void {
    this.toDynamicValue(
      (context) => context.container.get<T>(service)
    );
  }

Was using get method that throws exception when it would return promise. It caused prevented resolution of service using getAsync method.
getAsync could not be used instead because it always return promise even when resolution returns simple value (async keyword on function have that effect)
Removal of async keyword would change getAsync result - it would work for clients using await because one can await simple value but it would break for clients calling then/catch because simple values does not have them.
New function getMaybeAsync was introduced instead to Container interface returning promise when resolved to promise and simple value when resolved to simple value.

If introduction of new interface method is not desired then I see another way to approach problem - by passing if resolution is sync/async through Context.

Related Issue

#1409

Motivation and Context

toService binding were using Container.get method internally so it was throwing exception when the binding target was promise even if the resolution was also asynchroneous (getAsync)

How Has This Been Tested?

Added new automated test case.
All old test cases are passing.

Types of changes

• Updated docs / Refactor code / Added a tests case (non-breaking change)
• Bug fix (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 change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have updated the changelog.

I will update changelog/documentation if general shape of PR is acceptable.

[notaphplover]

#1635 solved this issue