[CT-3488] [Feature] Generate manifest at build time or in PR

### 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 functionality, rather than a Big Idea better suited to a discussion

### Describe the feature

Currently dbt-core relies on a delicate mechanism to generate a manifest: https://github.com/dbt-labs/dbt-core/blame/6e0a38720529360d061bd4e24e140f5ec55f8c15/tests/functional/artifacts/test_previous_version_state.py#L414

Instead of relying on commenting/uncommenting out test code we should generate this as part of our CI process either on the PR or in the release.

The current setup risks us to accidentally merge a manifest change: https://github.com/dbt-labs/dbt-core/pull/9195#discussion_r1423169447 and is unintuitive for core development

### Describe alternatives you've considered

_No response_

### Who will this benefit?

_No response_

### Are you interested in contributing this feature?

_No response_

### Anything else?

_No response_