Elide Hashicorp from docs

[iwahbe]

Cleanup inspired by #1660.

Solving #1660 requires a deeper dive into how code cleanup relates to examples.

[VenelinMartinov]

Should we really elide the examples? They might be perfectly valid otherwise. I think there's a precedent in AWS of replacing instead: https://github.com/pulumi/pulumi-aws/blob/8dc14b16493458bd85a374fbd37c50084718a827/provider/replacements.json#L434

Can't we do something like that here too?

[iwahbe]

Should we really elide the examples? They might be perfectly valid otherwise.

That is what we do with terraform, and is consistent with our existing strategy.

I think there's a precedent in AWS of replacing instead: https://github.com/pulumi/pulumi-aws/blob/8dc14b16493458bd85a374fbd37c50084718a827/provider/replacements.json#L434

Can't we do something like that here too?

AWS does this (as a custom pre-processor step), but the replaces are manual. If a replace is missed, it still elides. I'd be happy to build up a more robust set of replaces to fix elided docs.

[VenelinMartinov]

This looks like a strict regression to me - the examples in #1660 are functionally fine, so I don't see why we would elide them.

Shouldn't we just replace ".*@hashicorp.com" with ".*@example.com" everywhere?