[CI/CD Improvements] Standardize and automate formatting for workflows

[mikealfare]

Is this your first time submitting a feature request?

• I have read the expectations for open source contributors
• I have searched the existing issues, and I could not find an existing issue for this feature
• I am requesting a straightforward extension of existing dbt-postgres functionality, rather than a Big Idea better suited to a discussion

Describe the feature

As a maintainer, I want to automate formatting checks, so that I can focus more on content in PRs and still maintain a code quality standard.

Acceptance Criteria

Preview Give feedback

1. A formatter runs as part of pre-commit
2. A linter runs as part of pre-commit
3. docs-issue, stale, and triage-labels are updated to use the naming standards below (other workflows will be updated as separate stories; these workflows require no other changes)

Formatters:

• pretty-format-yaml @ https://github.com/macisamuele/language-formatters-pre-commit-hooks
• yamlfmt @ https://github.com/jumanjihouse/pre-commit-hook-yamlfmt
• yamlfmt @ https://github.com/google/yamlfmt (requires Go)
• Something that can be run via pre-commit hooks and which can enforce the style standards

Linters:

• check-yaml @ https://github.com/pre-commit/pre-commit-hooks
• yamllint @ https://github.com/adrienverge/yamllint
• Something that can be run via pre-commit hooks

Style standards:

• Job ids, step ids, and variables are in kebab case
• Job names, step names, and description fields follow dbt docs standards (capitalize first word only)
• Extra descriptors should be avoided unless required for disambiguation, e.g.
  • version-number -> version
  • archive-name -> archive
• Workflow files use a four space tab
• Scripts (inline or separate files) use environment variables in env instead of inline substitution like ${{ inputs.value }}