Component resources shouldn't have id properties

[danielrbradley]

Problem description

All custom resources have an id output field which is not part of the schema but is added by the SDK (and docs).

However, component resources do not have an id added by the SDK, but the docs do still add the id field.

E.g. https://www.pulumi.com/registry/packages/awsx/api-docs/ec2/vpc/#id_csharp

Suggestions for a fix

We should add an exception to the docs generation process to not add id fields to component resources.

[justinvp]

Here's where this is set:

pulumi/pkg/codegen/docs/gen.go

Lines 1561 to 1566 in 449307d

	// All resources have an implicit `id` output property, that we must inject into the docs.
	filteredOutputProps = append(filteredOutputProps, &schema.Property{
	Name: "id",
	Comment: "The provider-assigned unique ID for this managed resource.",
	Type: schema.StringType,
	})

The fix: if r.IsComponent, then the id property should not be added.