[Feature] Make `DBT_SECRET_ENV` prefixes available in run-operation macros

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

As of today, `DBT_SECRET_ENV` env_vars are only allowed in a `profiles.yml` or packages, greatly limiting the potential for using dbt to idempotently but securely configure target DBs.

`run-operation` commands would greatly benefit from the availability.

If too general, a `run-secret-operation` which is prohibited by default from generatingany output should be available.

### Describe alternatives you've considered

Coming up with a separate, standalone logic to run this, i.e. either with standalone Python or DuckDB.

### Who will this benefit?

All dbt users.

### Are you interested in contributing this feature?

_No response_

### Anything else?

_No response_