Custom type named FileXyz triggers content type workaround

There's a workaround that auto-sets content type form-data if it sees a payload entry of type `File`, but it matches for any (custom) types starting with "File" in JSON payloads, thus making them content-type form-data suddenly.