Closes ENG-856

Incorporates @galvana's change in the memory-watch branch, and adds tests and cleans up testing connector.

The testing connector can still be obtained from this branch: ENG-856-memory-manager-testing-setup and also includes commenting out some code that I had to modify on order to get the testing connector to load on my machine.

Code Changes

• Adrian's memory watchdog
• Configuration to enable the memory watchdog (defaults to off)
• Tests that prove the configuration works and tests for the memory watchdog itself

Steps to Confirm

1. Verify the configuration using this API call:

curl --request PATCH
--url 'http://localhost:3000/api/v1/config?api_set=true'
--header 'Authorization: Bearer YOUR_TOKEN'
--header 'Content-Type: application/json'
--data '
{
"execution": {
"memory_watchdog_enabled": true
}
}'

Followed by a GET to the same endpoint

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required