docs: Consider replacing terraform with pulumi globally

[guineveresaenger]

The current status quo for registry docs "sections" (not including actual code snippets; see #2248 for that) is as follows:

1. The bridge detects the mention of "Terraform"
2. The bridge elides the entire section from the schema
3. We miss out on a lot of examples and top-level content

Previously, the reason we elide sections that include the word "Terraform" was that we assumed such a section would very specifically talk about Terraform concepts. In practice, this is often untrue, and we lose quite a lot of content with this strategy.

We should consider a default edit rule that is a bit wider or even global in scope.

Note We need to consider that the detection logic for transforming pulumi import currently relies on seeing terraform import in the passed-in docs section. That would need to change.

[flostadler]

There is an instance of this biting AWS users pretty hard: pulumi/pulumi-aws#4872
This is a rather dangerous resource, that has multiple warnings in Terraform and we dropped them because they included the word Terraform.

Having a global rule would've been better here. Even mentioning Terraform instead of Pulumi would've been better in this case

[guineveresaenger]

Another example of missing documentation: pulumi/pulumi-gcp#2739; in this case the affected section is a field description, not a top-level doc, but the same thoughts apply.