Custom fields in data use declaration form

[TheAndrewJackson]

Closes #3177

Code Changes

• Make the custom field location readonly when editing a custom field
• Make name and data use readonly when editing a privacy declaration
  • This was done in the datamap PD form as well but in a very hardcoded way. This is intentional because the separate forms are about to be merged together in Merge "forked" PrivacyDeclaration components #2976
• Add custom fields to the privacy declaration form (in the portal only)

Steps to Confirm

• Run fidesplus (nox -s "dev(slim)") backend and admin ui
• Create some custom fields that have the system:data use location and create a system
• Create a a few new privacy declarations with data in the custom fields. Make sure that the new PD maintains it's custom field data after the save
• Edit all of the PDs and make sure the edited custom field data persists as expected
• Make sure the name and data use fields should be read only when editing

Pre-Merge Checklist

• All CI Pipelines Succeeded
• Documentation:
  • documentation complete, PR opened in fidesdocs
  • documentation issue created in fidesdocs
• Issue Requirements are Met
• Relevant Follow-Up Issues Created
• Update CHANGELOG.md
• For API changes, the Postman collection has been updated

Description Of Changes

example.mov

[cypress]

Passing run #1692 ↗︎

0

4

0

0

0

Details:

Merge 3054d34 into a0c26a8...
Project: fides	Commit: 9b30b89de9 ℹ️
Status: Passed	Duration: 00:59 💡
Started: May 2, 2023 12:38 PM	Ended: May 2, 2023 12:39 PM

_{This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.}

[allisonking]

looking good!! definitely some refactoring we can do but we can do a good chunk of it in #2976. I left some comments most of which can be TODOs—the only one that I'm slightly concerned about is that fidesKey thing on custom fields (I'm worried I removed it without seeing the consequence!)