1204 - Configure Connector after creation

[chriscalhoun1974]

Closes #1204

Code Changes

• Configure option has been added to the hamburger menu for each connection listed on the Datastore Connections landing page
• New route has been configured (/datastore-connection/[id]) for when the user clicks the Configure option, the browser window will navigate to a new URL such as http://localhost:3000/datastore-connection/my_manual_webhook_1
• Datastore Type and System Type dropdown menus have been updated on the Datastore Connections landing page to mirror the Choose your connection page
• Set focus to Username input text box on login page and added autocomplete="off" attribute to Username and Password input text boxes

Steps to Confirm

1. Login to Fides Admin UI
2. Click the Datastore Connections link
3. If no connection(s) exist, click Create New Connection and complete the create connection workflow
4. If connection(s) exist, click the hamburger menu item and select the Configure option
5. Browser window will navigate to a URL such as http://localhost:3000/datastore-connection/my_manual_webhook_1
6. User can edit values for a given Manual, Database, or 3rd party integrations connector connection (Connector parameters, Dataset configuration, or DSR customization screens)

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)
• [x] Issue Requirements are Met
• [ ] Relevant Follow-Up Issues Created
• [x] Update CHANGELOG.md

Description Of Changes

NOTE: Currently if a user were to select an option from the Datastore Type dropdown which is a Saas connector type, the API does not support this filtering feature at this time. In addition, if a user were to click the Manual connectors option from the the System Type dropdown, the API does not support this filtering feature as well. Experience Team will address this issue in the next upcoming sprint.