1746 fides connector

[adamsachs]

Closes #1746
Closes #1747

Code Changes

• New fides connector/connection type that forwards a privacy request to "child" Fides instances whose details are provided via connector config secrets
  • the new authenticated privacy request endpoint is invoked on the child, meaning that the fides connector config needs to have valid credentials (username and password) for the child server
  • DB migration for the new fides connection type is also included
• Also provides a helper function to filter out datasets that belong to a Fides connector connection config. We use this helper in the request runner to identify these datasets, because they will require some further "special-cased" post-processing in the graph aggregation/result upload (that will be covered in a subsequent PR)
• Automated tests to cover the above functionality, including some integration tests that interact with a running Fides server
• Included some nox and docker options to spin up a test environment locally that mimics a parent/child setup, with two running fides instances. I've used this environment to manually verify end-to-end functionality

Steps to Confirm

• nox -s dev -- child remote_debug
  • the remote_debug flag is optional but can be useful here
• docker exec -ti fides-fides-1 /bin/bash and then python scripts/load_fides_child_examples.py to configure the fides connector config on the "parent" fides
• configure any valid connector on the "child" fides via API (it should be accessible at http://0.0.0.0:8081 from a host machine)
• submit a privacy request against the "parent" fides and confirm that results are output to whatever storage location is configured on the policy
  • e.g.

curl --location --request POST 'http://0.0.0.0:8080/api/v1/privacy-request' \
--header 'Content-Type: application/json' \
--data-raw '[
    {
        "identity": {"email": "[email protected]"},
        "policy_key": "default_access_policy"
    }
]'

Pre-Merge Checklist

• All CI Pipelines Succeeded
• Documentation Updated:
  • documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
  • documentation issue created (tag docs-team to complete issue separately)
• Issue Requirements are Met
• Relevant Follow-Up Issues Created
• Update CHANGELOG.md

Description Of Changes

Initial implementation of Fides connector functionality. Does not include result aggregation functionality, as that will be covered in a subsequent PR.

[sanders41]

Looks good. Just a couple minor questions/suggestions.

[sanders41]

lgtm