kubernetes.yaml.ConfigFile shouldn't pass providers to the child resources it creates

[ringods]

What happened?

When passing explicit providers (plural!) to ConfigFile, one gets this error:

kubernetes:yaml:ConfigFile (guestbook):
    error: Error: Do not supply 'providers' option to a CustomResource. Did you mean 'provider' instead?
        at new CustomResource (/Users/vivek/code/examples/gcp-ts-gke-hello-world/node_modules/@pulumi/resource.ts:769:19)
        at new Service (/Users/vivek/code/examples/gcp-ts-gke-hello-world/node_modules/@pulumi/core/v1/service.ts:152:9)

Steps to reproduce

See the example from @viveklak in pulumi/pulumi#9996

Expected Behavior

ConfigFile implementation should strip providers from the opts before passing it the child resources.

Actual Behavior

The parent is added to the opts to point to the ConfigFile instance. The rest is passed unmodified as well, including providers:

pulumi-kubernetes/sdk/nodejs/yaml/yaml.ts

Lines 2809 to 2819 in 763ddca

	this.resources = pulumi.output(text.then(t => {
	try {
	return parseYamlDocument({
	objs: yamlLoadAll(t, opts),
	transformations,
	resourcePrefix: config && config.resourcePrefix || undefined
	}, {...opts, parent: this})
	} catch (e) {
	throw Error(`Error fetching YAML file '${fileId}': ${e}`);
	}
	}));

Versions used

Latest k8s provider still has this bug.

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).