…lements using the standard format (YYYY-MM-DD or YYYY-MM-DDTHH:mm:ss), and "datetime" elements are converted into "datetime-local" (datetime is deprecated/obsolete).

• Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  Fixes Not including 'format' option in schema for an 'inputType: date' fails v2.2.2 #480 - dates are always passed to the HTML5 "date" or "datetime-local" element in the correct format. "datetime" is also converted into "datetime-local" as "datetime" is now deprecated/obsolete

• What is the current behavior? (You can also link to an open issue here)
  When a "format" is not provided, the date/datetime field would be sent a number and throw an exception formatting the value

• What is the new behavior (if this is a feature change)?
  values are always passed to date/datetime-local field in the correct "YYYY-MM-DDTHH:mm:ss" format as described in the docs

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
  It should not

• Other information:
  Refer to Not including 'format' option in schema for an 'inputType: date' fails v2.2.2 #480