Adopt plain types in the schema to match the implementation

[justinvp]

There are cases where inputs to some components in the TS implementation are plain, but the schema doesn’t indicate they are plain (EKS was originally schematized before plain values were supported in the schema), so it’s possible someone could pass an Output<T> for these from multi-lang, which may result in problems in the implementation if it isn't expecting an Output<T> value.

Fixes #817

[github-actions]

Does the PR have any schema changes?

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

[justinvp]

These are non-plain Input<T> in the schema:

pulumi-eks/provider/cmd/pulumi-gen-eks/main.go

Lines 619 to 624 in c6f1fce

	"region": {
	TypeSpec: schema.TypeSpec{Type: "string"}, // TODO: enum: consider typing as `aws.Region`
	},
	"profile": {
	TypeSpec: schema.TypeSpec{Type: "string"},
	},

And they can easily be made Input<T> in the implementation, as they're just passed along through getRoleProvider, which passes them as inputs when creating aws.Provider, which already accepts Input<T> for these:

pulumi-eks/nodejs/eks/cluster.ts

Lines 331 to 333 in c6f1fce

	const creatorProvider = new aws.Provider(`${name}-eksClusterCreatorEntity`, {
	region: region,
	profile: profile,

[github-actions]

Does the PR have any schema changes?

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

[github-actions]

Does the PR have any schema changes?

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

[github-actions]

Does the PR have any schema changes?

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

[danielrbradley]

This looks great 👏

Might be a couple more of these that we can make inputty, but that's a non-breaking change we can revisit another day.