Reorder package manipulation in ckanext-spatial

[nickumia-reisys]

User Story

In order to reduce harvesting errors, the Data.gov Harvesting Team wants to keep a ckanext-spatial customization around.

Acceptance Criteria

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

• GIVEN [a contextual precondition]
  [AND optionally another precondition]
  WHEN [a triggering event] happens
  THEN [a verifiable outcome]
  [AND optionally another verifiable outcome]

Background

• Reintegrate ckanext-spatial upstream into catalog.data.gov #3938

Per @jbrown-xentity:

I think we can move forward without the fix about deleting before re-creating; however I think it may cause issues with downstream users like geoplatform, and some of our CSDGM datasets. I think the way some downstream users update their data causes our system to replace them (destroy and re-create), which then causes links to change and other problems for our consumers

Security Considerations (required)

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

Sketch

[Notes or a checklist reflecting our understanding of the selected approach]