BUG :: json-schema built-in formats not always used

[gdbrown]

Anywhere there's a possibility to use a built-in format it should populate the format property.
http://spacetelescope.github.io/understanding-json-schema/reference/string.html#built-in-formats

Example where it doesn't:

    "ctx_ip": {
      "type": "string",
      "minLength": 0,
      "maxLength": 255,
      "pbj": {
        "type": "string",
        "rule": "single",
        "format": "ipv4",
        "overridable": true
      }
    },

There are also our custom formats that are not enforced by a pattern...

    "provider": {
      "type": "string",
      "minLength": 0,
      "maxLength": 20,
      "pbj": {
        "type": "string",
        "rule": "single",
        "format": "slug"
      }
    },

Using format of slug on a pbj must result in a pattern on the item with the slug regex pattern, which is in StringType in pbj. see StringType and Format class in pbj lib, ref aws3 branch

[gdbrown]

when a format that we use internally is not a public format (like ipv4) then it should be a regex pattern with the proper type (for example, slug would be type string and we'd put in the regex to validate it)