fix(idp-extraction-connector): added custom deserialization for headers map

[reiballa]

Description

Fixes deserialization of [openAiHeaders](vscode-file://vscode-Fixes deserialization of openAiHeaders (Map<String, String>) in the IDP Extraction connector when FEEL evaluation is disabled for outbound connectors.

Since PR #6210 introduced a separate outboundConnectorObjectMapper with @feel processing disabled, Map-typed fields that arrive as JSON strings can no longer rely on the FeelDeserializer to coerce them. This caused a MismatchedInputException at runtime.

Testing:

• Added StringToMapDeserializerTest to verify correct deserialization from both JSON objects and strings, and to ensure invalid inputs are properly rejected.

Related issues

closes #6935

Checklist

• Backport labels are added if these code changes should be backported. No backport label is added to the latest
  release, as this branch will be rebased onto main before the next release. Example backport labels:
  • backport stable/8.8: for changes that should be included in the next 8.8.x release.
  • or backport release-8.8.7: for changes that should be included in the specific release 8.8.7, and this
    release has already been created. The release branch will be merged back into stable/8.8 later, so the change
    will be included in future 8.8.x releases as well.
• Tests/Integration tests for the changes have been added if applicable.
• If the change requires a documentation update, it has been added to the appropriate section in the documentation.

[Copilot]

Pull request overview

Fixes runtime deserialization failures for openAiHeaders in the IDP Extraction connector when FEEL processing is disabled by introducing a custom Jackson deserializer that accepts either a JSON object or a JSON-encoded string.

Changes:

• Added StringToMapDeserializer (and unit tests) to coerce Map<String, String> from either object or JSON-string inputs.
• Applied the custom deserializer to openAiHeaders in both OpenAiRequest and OpenAiProvider.
• Sanitized OpenAI custom header values before passing them to the underlying HTTP client/model builder.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
connectors/idp-extraction/src/main/java/io/camunda/connector/idp/extraction/jackson/StringToMapDeserializer.java	New deserializer to support object-or-string map inputs for headers.
connectors/idp-extraction/src/test/java/io/camunda/connector/idp/extraction/jackson/StringToMapDeserializerTest.java	Unit tests covering valid object/string inputs and invalid inputs.
connectors/idp-extraction/src/main/java/io/camunda/connector/idp/extraction/request/common/ai/OpenAiRequest.java	Uses the new deserializer for openAiHeaders during variable binding.
connectors/idp-extraction/src/main/java/io/camunda/connector/idp/extraction/model/providers/OpenAiProvider.java	Uses the new deserializer for provider-level openAiHeaders.
connectors/idp-extraction/src/main/java/io/camunda/connector/idp/extraction/client/ai/OpenAiClient.java	Sanitizes header values prior to configuring the OpenAI chat model.

[steven-rg-harrison]

One minor comment, but not a blocker

[team-connectors-int-automation]

Successfully created backport PR for stable/8.9:

• [Backport stable/8.9] fix(idp-extraction-connector): added custom deserialization for headers map #6948

[github-actions]

🎉 This pull request has been included in release 8.9.1!

Thank you for your contribution! 🚀

[github-actions]

🎉 This pull request has been included in release 8.10.0-alpha1!

Thank you for your contribution! 🚀