Improve GH Issue Labels

[jkodroff]

The labels on this repo are the generic labels we use for all of our more code-centric repos. We should make them make sense for this repo in order to improve our ability to track quality and areas that need attention across the docs.

A modest proposal:

For issues relating to content:

• content/blog
• content/www (marketing pages)
• content/iac
• content/esc
• content/idp
• content/deployments
• content/tutorials
• content/pulumi-cloud (for miscellaneous stuff like RBAC or SSO)

For issues relating to engineering:

• engineering/automation (CI/CD, the automated docs generation processes, linting, etc.)
• engineering/front-end (styling)
• (Anything else to add here?)

Keep the following as-is:

• p0/p1/p2
• resolution/*
• kind/* (consider adding kind/seo)

Remove everything else.

[jkodroff]

Note that the issues on this repo are managed by https://github.com/pulumi/team-management, so we'd need to allow the ability to override the defaults in that repo.

@thoward If we can figure out what the desired state is in this issue, that would still be progress. I think it basically comes down to team ownership in the org chart and who can verify technical information when SME is needed.