Deprecate patch_datasets and patch_yaml_datasets endpoints

[pattisdr]

❗ Depends on #1766 ❗

Is your feature request related to a specific problem?

Currently datasets are stored in two places for different use cases, on the DatasetConfig.dataset table and in the ctl_datasets table. Our unified fides resources work is moving to storing this in ctl_datasets.

A new endpoint, patch_dataset_configs is being added. After the UI is in to use this endpoint, the other endpoints can be deprecated.

Describe the solution you'd like

• Deprecate PATCH {{host}}/connection/{{connection_key}}/dataset.
• Deprecate PATCH {{host}}/yml/connection/{{connection_key}}/dataset
• Deprecate GET {{host}}//connection/{{connection_key}}/dataset
• Deprecate GET {{host}}//connection/{{connection_key}}/dataset/{{datasetconfig_key}}
  • Have endpoint return a message that the endpoint is deprecated and direct them to their replacement (/datasetconfig endpoints)

Describe alternatives you've considered, if any

A description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

[pattisdr]

Also switch any other remaining instances in the codebase to use the new patterns (upsert to CTL Dataset then PATCH to Dataset Config).

• nox -s test_env for example, calls the PATCH /connection/connection_key/dataset endpoint we'd like to deprecate
• The quickstart too
• What else?

EDIT: went ahead and addressed this point here: #2225

[pattisdr]

This doesn't block the release of unified-fides-resources.

[pattisdr]

Also need to discuss what our deprecation policy is.

Motivations to deprecate: These endpoints on the unified-fides-resources branch now potentially have surprising updates, in that they not only update the datasetconfig but the associated ctl dataset.

While we can change all of our code to not make calls to these endpoints, is anyone relying on these?