[Epic] Implement current "overlay" resources in the provider binary

[AaronFriel]

The following resources are implemented as "overlay" resources, hand-written in each of our supported languages. This has increased the cost of supporting these resources and ensuring they handle resource options such as dependsOn.

• Document dependsOn limitations for ComponentResource resources (Helm, YAML, Kustomize) #1773
• Helm v3 Chart does not convert input properties to output properties #1923
• Pass provider options to all invokes in component resources #1945
• [Python] MyPy Error on Output.all(ConfigFile().resources) #1729
• pulumi refresh targeting a yaml.ConfigFile or yaml.ConfigGroup should refresh all generated resources #1642
• Support dependsOn for YAML ConfigFile/ConfigGroup #1833
• & more

These resource types are currently only available as overlays:

• kubernetes:apiextensions.k8s.io:CustomResource
• kubernetes:kustomize:Directory
• kubernetes:yaml:ConfigFile
• kubernetes:yaml:ConfigGroup

And the Helm Chart resources have an upgrade path via Helm/v3 Release:

• kubernetes:helm.sh/v2:Chart
• kubernetes:helm.sh/v3:Chart

### Tasks
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/2788
- [ ] https://github.com/pulumi/pulumi/pull/15488
- [ ] https://github.com/pulumi/pulumi/pull/15490
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/2784
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/2785
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/2871
- [ ] https://github.com/pulumi/pulumi/issues/15681
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/2870
- [ ] https://github.com/pulumi/pulumi-kubernetes/pull/2900
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/2868
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/2847
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/2787
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/2786
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/2181
- [ ] https://github.com/pulumi/pulumi-kubernetes/pull/2918
- [ ] Update the "pulumi new" template
- [ ] Add new examples
- [ ] Write post-mortem

### Resolves
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/1833
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/1773
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/1960
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/1689
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/1208
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/1174
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/1173
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/1108
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/907
- [ ] https://github.com/pulumi/pulumi-kubernetes/issues/1923

[EronWright]

Some questions to resolve:

1. are there blocking upstream issues (e.g. codegen, transform support in MLCs)?
2. how would this be delivered (e.g. new provider vs. new resources in k provider).
3. which overlay resources are specifically being developed? (e.g. Chart, Release, Directory, ConfigGroup, ConfigFile)

[lblackstone]

master...lblackstone/mlc has a proof on concept for this work.