Move the migrations package into the fidesops package

[PSalant726]

Purpose

When installing fidesops via PyPI, the migrations package is installed outside of the fidesops package source tree, in a sibling directory of /fidesops. Currently there is no way to specify a path to DB migrations that exists outside of the /fidesops package source tree.

The fidesops-plus repository requires access to the database migrations in order to start the API server.

Changes

• Move the migrations package into the core fidesops package
• Update all references to the /migrations directory
• Remove the now unused PackageSettings class

Checklist

• Update CHANGELOG.md file
  • Merge in main so the most recent CHANGELOG.md file is being appended to
  • Add description within the Unreleased section in an appropriate category. Add a new category from the list at the top of the file if the needed one isn't already there.
  • Add a link to this PR at the end of the description with the PR number as the text. example: #1
• Applicable documentation updated (guides, quickstart, postman collections, tutorial, fidesdemo, database diagram.
• If docs updated (select one):
  • 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)
• Good unit test/integration test coverage
• This PR contains a DB migration. If checked, the reviewer should confirm with the author that the down_revision correctly references the previous migration before merging
• The Run Unsafe PR Checks label has been applied, and checks have passed, if this PR touches any external services

Ticket

Fixes #615

[sanders41]

Before merging this we will need to figure out the best way to handle open PRs that contain migrations. I know at least @pattisdr has a PR with a migration.

I guess a rebase and moving the migration file would work?

[pattisdr]

thanks for the heads-up on migrations Paul, since #591 was just merged, that's one migration that will need to be moved before this work is merged

[PSalant726]

I guess a rebase and moving the migration file would work?

@sanders41 Yea exactly. In the past we've unfortunately just had to ask anyone with open PRs to rebase once a PR like this one is merged.

@pattisdr I've merged in main and handled the new migration from #591. Thanks for the heads up!

[sanders41]

@PSalant726 All looks, but there is a merge conflict with CONTRIBUTING.md now.