Component option propagation (Python SDK)

[EronWright]

Proposed changes

Epic: #2254
Fixes: #2356

This PR standardizes the option propagation logic for the component resources in the pulumi-kubernetes Python SDK. The general approach is:

1. In the component resource constructor, compute the child options to be propagated to any children. The child options consist of the component as parent, and with version and pluginDownloadURL if specified.
2. Compute the invoke options by copying the child options.

Specification

The component resource is responsible for computing sub-options for invokes and for child resource declarations. This table outlines the expected behavior for each resource option when presented to a component resource.

	Propagated	Remarks
additionalSecretOutputs	no	"does not apply to component resources"
aliases	no	Inherited via parent-child relationship.
customTimeouts	no	"does not apply to component resources"
deleteBeforeReplace	no
deletedWith	no
dependsOn	no	The children implicitly wait for the dependency.
ignoreChanges	no	Nonsensical to apply directly to children (see discussion).
import	no
parent	yes	The component becomes the parent.
protect	no	Inherited.
provider	no	Combined into providers map, then inherited via parent-child relationship.
providers	no	Inherited.
replaceOnChanges	no	"does not apply to component resources"
retainOnDelete	no	"does not apply to component resources"
transformations	no	Inherited.
version	yes	Influences default provider selection logic during invokes. Should propagate when child resource is from the same provider type.
pluginDownloadURL	yes	Influences default provider selection logic during invokes. Should propagate when child resource is from the same provider type.

Testing

A new test case is provided (test case, test program) that exercises option propagation across the component resources:

• kubernetes.helm.sh.v3.Chart
• kubernetes.kustomize.Directory
• kubernetes.yaml.ConfigGroup
• kubernetes.yaml.ConfigFile

Upgrade testing must be done manually, with an emphasis on avoiding replacement due to reparenting.

Related issues (optional)

[github-actions]

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.