Remove harvest related code/tests from ckanext-geodatagov for catalog-next

[FuhuXia]

User Story

In order to have less code and tests to maintain, data.gov team wants to remove harvest related code from ckanext-geodatagov for catalog-next

Acceptance Criteria

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

• no ckanext-harvest dependency.
• no harvest related code and tests

Background

[Any helpful contextual notes or links to artifacts/evidence, if needed]

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]

[FuhuXia]

On second thought, this should not be part of catalog 2.11 upgrade.

[Bagesary]

Iceboxing this ticket as this will not be part of catalog 2.11 upgrade