Add connection type dropdown advanced properties

[emilys314]

Completes https://issues.redhat.com/browse/RHOAIENG-10322

Description

• This adds the "Advanced settings" dropdown / expandable form to the dropdown creation modal. It is defaulted to open when you select the dropdown variant (because there are required options).
• The single select variant is automatically selected.
• The table has draggable rows, and they can be deleted and added. A minimum of 1 row will always exist.
• The "Dropdown item values" is the required field, so an option can exist without a label. In this scenario, I default the label to be the value.
• The default values will be updated with the list of options from the table row. Blank options will not be added. If an option has a blank value, it will still be added, but the option will be disabled until a value is added.
• If there are duplicate values in the table, currently the creation will be disabled. There isn't any design on how to handle this yet.
• If a item has been selected as a default value, and you modify that item (like delete it or change the value), the default value will be removed (so it's not orphaned)

Initial state

Single select with options:

Multi select with options (and 1 blank option that is omitted):

Single select with options (1 is missing a label, a 2nd is missing a value)

How Has This Been Tested?

1. Go to /connectionTypes/create
2. Add a new field
3. Select field type of "dropdown"
4. New changes appear

Test Impact

Jest tests have been added like the other advanced forms to test all the functionality of the component

Request review criteria:

Self checklist (all need to be checked):

• The developer has manually tested the changes and verified that the changes work
• 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.
  @simrandhaliw

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

[codecov]

Codecov Report

Attention: Patch coverage is 85.33333% with 11 lines in your changes missing coverage. Please review.

Project coverage is 85.16%. Comparing base (18061ba) to head (10bad63).
Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
...manage/advanced/DropdownAdvancedPropertiesForm.tsx	84.44%	7 Missing ⚠️
...c/pages/connectionTypes/manage/manageFieldUtils.ts	50.00%	2 Missing ⚠️
...cepts/connectionTypes/fields/DropdownFormField.tsx	96.00%	1 Missing ⚠️
...anage/advanced/DataFieldAdvancedPropertiesForm.tsx	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3143      +/-   ##
==========================================
+ Coverage   85.13%   85.16%   +0.02%     
==========================================
  Files        1250     1251       +1     
  Lines       27272    27332      +60     
  Branches     7209     7233      +24     
==========================================
+ Hits        23219    23276      +57     
- Misses       4053     4056       +3     

Files with missing lines	Coverage Δ
...cepts/connectionTypes/fields/DropdownFormField.tsx	84.31% <96.00%> (+4.31%)	⬆️
...anage/advanced/DataFieldAdvancedPropertiesForm.tsx	58.82% <0.00%> (-5.89%)	⬇️
...c/pages/connectionTypes/manage/manageFieldUtils.ts	63.63% <50.00%> (-7.80%)	⬇️
...manage/advanced/DropdownAdvancedPropertiesForm.tsx	84.44% <84.44%> (ø)

... and 5 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 18061ba...10bad63. Read the comment docs.

[christianvogt]

Do we care if labels are the same? Imo labels should differ. But since we render the value at all times as well it doesn't really matter to have unique labels.

[emilys314]

Good question, maybe we followup alongside the warning of duplicate values

[christianvogt]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: christianvogt

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