[api/suggestion] DRY with `CustomResourceOptions` context

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

This is low priority.

When working with kubernetes, I find that I have to pass CustomResourceOptions everywhere.

I would like to follow DRY.

old

    final var clusterResourceOptions = CustomResourceOptions
        .builder()
        .provider(clusterProvider)
        .build();
    new Deployment("myDeployment1", myDeploymentArgs1, clusterResourceOptions);
    new Deployment("myDeployment2", myDeploymentArgs2, clusterResourceOptions);
    new Deployment("myDeployment3", myDeploymentArgs3, clusterResourceOptions);

new(runWithCustomResourceOptions name subject to change)

Pulumi.runWithCustomResourceOptions(myCustomResourceOptions, () -> {
    new Deployment("myDeployment1", myDeploymentArgs1);
    new Deployment("myDeployment2", myDeploymentArgs2);
    new Deployment("myDeployment3", myDeploymentArgs3);
});

Affected area/feature

Start by reviewing the Java API entry points named in the proposal: CustomResourceOptions, Pulumi, and Deployment. Clarify the design and naming for runWithCustomResourceOptions, then establish how equivalent Deployment calls should inherit the options and what tests or examples will demonstrate that the explicit arguments are no longer required.