#3287 fix: Handle presence of `charset` in `Content-Type` header when retrieving schema from OpenAPI spec
Pull request opened by edgarrmondragon
SSIA.
## Summary by Sourcery
Fix detection of JSON and YAML content types by matching substrings in the Content-Type header, and update tests to cover headers with charset parameters.
Bug Fixes:
• Handle Content-Type header values containing 'application/json' or 'application/yaml' even when additional parameters (e.g., charset) are present
Tests:
• Add a test case for 'application/json; charset=utf-8' content type when loading OpenAPI schemas
meltano/sdk