Add central deprecation-warning pass for v1 removals

[ricardo-devis-agullo]

Summary

Implements #1529 (v1 Track 1 / non-breaking 0.x deprecation-warning work, see V1.md).

• Add a shared deprecate() utility (packages/oc/src/utils/deprecate.ts) that emits a consistent, once-per-process DeprecationWarning via process.emitWarning, naming the deprecated option and its replacement. This honors Node's standard --no-deprecation opt-out with no bespoke env var needed.
• Wire it into the registry config entry seam (options-sanitiser.ts) for: the s3 shortcut, refreshInterval, and the boolean form of discovery.
• Wire it into the CLI/local config entry seam (oc.json parser, ocConfig.ts) for the deprecated mocks block.
• No behavioral change: every deprecated option keeps resolving/merging exactly as before; the notices are purely additive.

Out of scope (tracked separately)

• Removing any of these options (the v1 change).
• Deprecating the callback registry/plugin/adapter APIs (tracked in Promise-first registry API (additive, dual callback/promise) [v1 0.x] #1528).
• tarExtractMode correction and adapter-neutral error codes.

Test plan

• New unit tests for the deprecate utility (dedup-per-id, message formatting) - test/unit/utils-deprecate.js
• New unit tests asserting the registry config seam calls deprecate for s3/refreshInterval/boolean discovery, and does not for well-formed config - test/unit/registry-domain-options-sanitiser-deprecation.js
• Extended test/unit/cli-domain-ocConfig.js to assert the mocks block triggers exactly one deprecation notice, and that normal config doesn't
• npm run build -w oc
• npm run test -w oc (953 passing)
• Added a changeset (oc: patch)

Generated with Devin