[Feature] Add `proto` generation and CI check as `hatch` command

### Is this your first time submitting a feature request?

- [X] I have read the [expectations for open source contributors](https://docs.getdbt.com/docs/contributing/oss-expectations)
- [X] I have searched the existing issues, and I could not find an existing issue for this feature
- [X] I am requesting a straightforward extension of existing dbt-adapter functionality, rather than a Big Idea better suited to a discussion

### Describe the feature

We should wrap the proto generation step in a `hatch` command for ease of use. We also want to make sure that this file is always up to date as a CI check.

### Describe alternatives you've considered

We considered running this as part of the build. However, we check in this file and this file is needed to run tests. So even though it feels like a build artifact, it's treated more like functional code; i.e. we should verify that it's correct with a test instead of creating or updating it.

### Who will this benefit?

This indirectly helps any user since it provides stability to the package. But ultimately, it just helps the maintainers.

### Are you interested in contributing this feature?

_No response_

### Anything else?

_No response_