TaskContext feature

[YaroBear]

TaskContext

• At the start of a pipeline execution, we should be able to hydrate some read-only store of configuration values. These values form a TaskContext that is available to every task. e.g. reading url for an endpoint we need to hit, or key vault secrets.
• Bonus points: Store hydrators are registerable. By default, the store is hydrated from a local .yml file. Additional hydrators can be registered by client applications that override the default.

[YaroBear]

We all took a stab in the pair coding session. The yml provider is in place!