Duplicate connection page UI

[emilys314]

Towards https://issues.redhat.com/browse/RHOAIENG-10314

Description

Adds the UI portion of the create / duplicate connection type page. The jira issue is for the duplicate page, but a lot of the create page is already made since it's dependent.

Error state:

How Has This Been Tested?

Manually on local. Start the front end and back end. Then go to the /connectionTypes/create or /connectionTypes/duplicate/<name> routes.

/duplicate requires an existing connection type. So you can go to /create and Make one first.

Test Impact

Cypress tests were added for create and duplicate pages.

Request review criteria:

Self checklist (all need to be checked):

• The developer has manually tested the changes and verified that the changes work
• Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

• Included any necessary screenshots or gifs if it was a UI change.
• Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

• The developer has tested their solution on a cluster by using the image produced by the PR to main

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[jenny-s51]

Duplicate page looks good and works as expected @emilys314 , tested by creating a data connection and was able to duplicate it successfully.

Just a note about the empty state table under Fields, would we want to use a default empty state rather than an empty state table? According to the mocks it looks like we don't want to show the table headers if there are no fields.

Otherwise LGTM!

[jenny-s51]

/lgtm

[ashley-o0o]

Tested locally, and ran the Cypress tests in the Cypress UI. Everything looking good on my end! One note, you'll need to squash commits before approval :)
/lgtm

[jeff-phillips-18]

/cc @simrandhaliw

[emilys314]

Tested locally, and ran the Cypress tests in the Cypress UI. Everything looking good on my end! One note, you'll need to squash commits before approval :) /lgtm

I think this is no longer the case. based on what i was seeing in some slack convos, the PR should squash it for you now

[christianvogt]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: christianvogt, jenny-s51

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• frontend/OWNERS [christianvogt]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment