Provider Configuration Refactor #143

What

The current provider manager configuration takes in ProviderInitConfig which conflates two concerns.
Construction policy and the Runtime Routing policy.
This must be separated and the factory must use the construction policy and provider manager should ideally depend on the runtime routing policy.
Additionally direct app provider resolution to use any specific provider should also be possible.

As part of the refactor, it may also be checked the need of optional provider and how integrator can configure it.
Update the documentation regarding the optional provider and how daemon behaves.

Acceptance Criteria (DoD)

Refactoring of provider configuration is done
Application provider resolution is supported

How

• Change the return type of the CreateAndRegister Provider to Expected<monostate, ErrorCode>
  No response