[dheerajitbhu]

Closes: #1140

get_record() JSON-parsed every application/json* content type, so a record saved as application/jsonl (or application/json-seq) could be written but not read back: response.json() failed and the client raised InvalidResponseBodyError.

Change

• _parse_get_record_response now JSON-parses only application/json and application/json…+json types (so application/json-patch+json keeps returning a dict, as today).
• Any other application/json* type, like application/jsonl or application/json-seq, is returned as text, matching how the JS client returns these records.
• The return-type question for +json types (string vs dict, as raised in the issue together with apify-client-js#1067) is left untouched on purpose.

Tests

• New parametrized sync and async tests in tests/unit/test_key_value_store.py cover application/json, application/json; charset=utf-8, application/json-patch+json, application/jsonl and application/json-seq against the mock server. The jsonl and json-seq cases fail on master (8 failures across both HTTP clients) and pass with the fix.
• ruff check, ruff format --check and the full unit suite (2627 passed) are green.

Disclosure: I maintain a few Apify Store actors, and this change was prepared with AI assistance and reviewed and tested by me.