selection: add DestinationField component and tests

[tony-tvu]

• Identified the issue which this PR solves.
• Read the CONTRIBUTING document.
• Code builds clean without any errors or warnings.
• Added appropriate tests for any new functionality.
• All new and existing tests passed.
• Added comments in the code, where necessary.
• Ran make check to catch common errors. Fixed any that came up.

Description:
This pull request introduces the DestinationField component, a crucial addition necessary to support the development of generic destinations with pluggable providers. The DestinationField component is designed to receive a destination type, such as single-field or multi-field destinations, as a prop and dynamically display the relevant information.

Which issue(s) this PR fixes:
Part of #2639

Screenshots:
Examples for single, multiple, and disabled destination types:

Additional Info:
Run make storybook to interact with DestinationField component.

This component will remain dormant within the main UI until they are integrated with upcoming component updates, such as the PolicyStepDialog components.

[Forfold]

Can we make it so the fields in storybook are editable/can type in?

Also, we'll need to add padding to the multi-input fields:

[tony-tvu]

Can we make it so the fields in storybook are editable/can type in?

Also, we'll need to add padding to the multi-input fields:

You can't edit the fields on the Docs page because those are just snapshots of all the tests. You can edit the fields when you go into individual test.