[TD] Consequence of `contentType` being optional

[danielpeintner]

The TD taskforce is discussing making contentType optional.

It is not only about ExpectedResponse and AdditionalExpectedResponse.
There are discussions that contentType MAY become optional in general and there is no default value kicking in like we do now with application/json.

I think we should try to understand the consequences (if any) from the Scripting API point of view.

[zolkis]

In real life not much consequence, since the underlying platform for Scripting includes bindings.
Anyway we should make sure to specify the applicable fallbacks.

When contentType is not available, the content could (should) be presented as null, or a byte stream, or byte array (based on the quoted discussion the latter would be enough).

[relu91]

Scripting api call 05/03/2025:

• to clarify it is still an ongoing discussion in TD so we have to wait until something concrete is decided.