[CI/CD Improvements] Create precommit-autoupdate workflow

[mikealfare]

Describe the feature

As a maintainer, I want to automate updating code quality dependencies, so that we're always on the latest version of these dependencies.

Acceptance Criteria

Beta Give feedback

1. All workflows adhere to the style standards below
2. If dependencies can be updated via precommit autoupdate, they are updated automatically on main (or the default branch) with no developer intervention
3. If dependencies cannot be updated via precommit autoupdate (e.g. mypy has a new check that fails for our code), an alert is sent to the appropriate alerts channel in Slack (e.g. #dev-adapter-alerts for an adapter)
4. I can easily add a new repo to this workflow, for example by updating a config file with the name of the repo and the associated alerts channel
5. This workflow runs on a regular cadence (e.g. weekly) and can also be triggered manually by providing a specific repo

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 }}