[Feature] Improve state:modified selector for parallel seed dependencies

### 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, when running `dbt build --select state:modified+`, the model simply runs any new/modified files along with any other files that depend on those new/modified files.

However, if we are running this command in a brand new schema (like with many PR-triggered jobs in dbt Cloud), this can be an issue if we update a seed file that affects a model _which depends on an unchanged seed file_.

Example:
We have a PR job that runs in dbt Cloud that creates a new schema. **Model A** depends on seed files **Seed 1** and **Seed 2**. We only made modfied **Seed 1**. However, when we run `dbt build --full-refresh --select state:modified+` , it doesn't bother creating **Seed 2** in the new schema. Thus, **Model A** fails stating there isn't any table created from **Seed 2**.

### Describe alternatives you've considered

The only way around this so far is to execute a full `dbt seed --full-refresh` first before running `dbt build --select state:modified+`

### Who will this benefit?

_No response_

### Are you interested in contributing this feature?

_No response_

### Anything else?

_No response_