fix(oci): 🐛 restore inline-PEM key normalization dropped during upstream sync [sc-553919]

[miguelangelmorenochacon]

Summary

The May 19 upstream-sync merge (PR #106, commit 03c53bc4b3) dropped the CARTO inline-PEM normalization block in litellm/llms/oci/chat/transformation.py but kept the upstream rename oci_key → oci_key_content in the private_key assignment. Net result: every OCI chat completion on this branch fails with NameError: name 'oci_key_content' is not defined at _sign_with_manual_credentials. Production (v1.83.3-carto.1.19.6) is unaffected because it predates the bad merge; ded-29 running this build is.

Root cause of the CI gap

.github/carto-features.yml is the manifest consumed by carto-features-check.yml to assert that critical CARTO patches survive each sync. The OCI Gemini tool-call feature (PR #68) was listed and the resolver restored it; the OCI inline-PEM feature (PR BerriAI#17159, 2905feb889) was not in the manifest, so the verifier had nothing to flag.

Changes

• litellm/llms/oci/chat/transformation.py — re-apply the dropped block: define oci_key_content, normalize escaped \n / \r\n sequences, reject non-string oci_key with OCIError, and switch the missing-key path from bare Exception to OCIError (both behaviors from feat(oci): Enable Oracle Cloud Infrastructure configuration via UI BerriAI/litellm#17159).
• .github/carto-features.yml — add OCI Inline PEM Key Normalization (source PR 17159) with two verification patterns so future syncs fail loud if this regresses.

Validation

tests/litellm/llms/oci/chat/test_oci_chat_transformation.py::TestOCIKeyNormalization — all 4 pass:

test_oci_key_with_escaped_newlines      PASSED
test_oci_key_with_crlf_newlines         PASSED
test_oci_key_rejects_non_string_type    PASSED
test_oci_key_rejects_list_type          PASSED

Manifest verifier locally — all 12 patterns OK (including the 2 new).

Story

sc-553919