[DPA-1357]: fix: include OCR secrets as part of deployment.Environment

[graham-chainlink]

There are many cases where a changeset requires access to the OCR secrets and because it is not accessible via deployment.Environment, users are left no choice but to pass secrets as config in a changesets. By plumbing OCR secrets in deployment.Environment, user will no longer need to do the workaround.

Update code to use OCR secrets from the env instead of from requests/config

JIRA: https://smartcontract-it.atlassian.net/browse/DPA-1357

Used by: https://github.com/smartcontractkit/chainlink-deployments/pull/253

[github-actions]

AER Report: CI Core ran successfully ✅

aer_workflow , commit

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

[cgruber]

Some solana things seem broken at this commit-point. I would rebase against latest, and see if the tests pass. It seems entirely unrelated to this PR.

[cgruber]

Looks good. We'll have to do the thing in CLD once this is done, of course. Once this is merged, changesets that use env.OCRSecrets will break until CLD primes the environments with them.

[cgruber]

This is great, but you'll have to do the instructions in this comment since you touched things in /core. It requires a different sort of "changeset" (a changelog notes system we use in core).

[graham-chainlink]

smartcontractkit/chainlink-deployments#253

Yes, this is the CLD PR that will consume this PR. I plan to merge that PR together with this once this is merged.

This is great, but you'll have to do the instructions in #15470 (comment) since you touched things in /core. It requires a different sort of "changeset" (a changelog notes system we use in core).

Cool, i have merge conflicts too , so will address them together.