fix #15393

This PR is part of the effort to split PR #17548

Adds a special case for handling deserialization of non-explicit doubles.

e.g, given the definition:

double_obj:
  properties:
    dfield:
      type: number
      format: double      

Then sending {dfield: 2.4} will deserialize correctly, but {dfield: 2} will be cast as an int an fail the object parse.

@jaumard (2018/09) @josh-burton (2019/12) @amondnet (2019/12) @sbu-WBT (2020/12) @kuhnroyal (2020/12) @agilob (2020/12) @ahmednfwela (2021/08)