Reorganize application code

[ThomasLaPiana]

Purpose

Reorganize the code to make the repo merger easier

Changes

• nest the application code down to match the fidesctl layout

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 #1005

[ThomasLaPiana]

@PSalant726 I'm assuming that the CodeQL warning is getting triggered because of the new Path?

[ThomasLaPiana]

documentation should have gotten updated here with the sweeping find and replaces, I'll take a look at what changed to double check though

[sanders41]

One thing I found in testing that I haven't found a reason for yet. I am having an issue with both nox -s dev and docker-compose up, when I try to login in from the admin-ui front end I get blocked. No log ever shows up on the server end as an attempted login. I compared the route the login page is using to the FastAPI docs route and everything looks correct. Maybe the CORS settings aren't getting applied?

Update:
I found the reason. It is browser specific. Things don't seem to work with Brave and it is unrelated to this update.

[PSalant726]

I'm assuming that the CodeQL warning is getting triggered because of the new Path?

Looks like a false positive because our variables contain the literal word "secret" ? My guess is that we dismissed a similar warning before the path changed, and now CodeQL is picking it up again.

The logging is not printing anything sensitive, so I think the warning can be dismissed. Someone with more context for this code should weigh in, just to be safe.

[sanders41]

There is one thing in the docs part that looks like it needs updating. Then every question after that is the same, are the .tmp files supposed to be there?

So it looks like a lot but the answer will be the same for all but one of the comments, so no need to reply directly to every one of them.

[ThomasLaPiana]

@sanders41 Aha, I know what happened with all of those tmp files. The find & replace took a toll on my computer (100+ files and automatic formatting) and VS code crashed, I'm assuming where those all came from, as they were in limbo waiting to be saved or something. Will delete them and update the docs page

[ThomasLaPiana]

@sanders41 I made some more thorough updates, would appreciate another review! 🙏

[sanders41]

lgtm. A crash would do it with the tmp files. Sounds like it was a fun update 😄

@seanpreston this one looks read to merge to me whenever you think it would be a good time.