update dcatus spatial schema value

[rshewitt]

User Story

In order to successfully validate certain records, datagov wants to update the spatial field in the dcatus schemas in ckanext-datajson to accept JSON objects.

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

• GIVEN the dcatus schemas in ckanext-datajson
  WHEN a JSON object is added as an acceptable value in the spatial field
  THEN records which have a JSON object as the spatial value will pass validation

Background

related to #5010

Security Considerations (required)

[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]

Sketch

• example. the first record should have it. in case the document changes here's what it looks like

"spatial": {
  "coordinates": [
  [
  -81.0563,
  34.9991
  ],
  [
  -80.6033,
  35.4024
  ]
  ],
  "type": "envelope"
  },

[jbrown-xentity]

We should consider this as changing the schema to be more lenient; spatial field may or may not be processed correctly.

[Bagesary]

Team will talk to Missouri customer and then pick this ticket up