Split form components into `Drupal`-prefixed behavioral wrappers and presentational components

Overview

Work on recent issues has identified evolving needs for our current implementation of the form components:

1. #3487484: Save page data form values in application state with support for undo/redo
   • Form element behaviors (data saving, validation etc.) needs to change based on context.
2. #3486888: Implement Storybook
   • Form elements need to be available as purely presentational components, decoupled from business logic, for efficient UI development.
3. #3483267: [exploratory] PoC of Preact+Tailwind components editable via CodeMirror
   • Form elements need to be available as purely presentational components, decoupled from business logic, to be used at other parts of the application — e.g. UI for defining props in JavaScript components.

Proposed resolution

Render each form component (ui/src/components/form/) by another component that wraps it in the `InputBehaviors` HOC. Prefix the name of these new components with `Drupal`.

This was proposed and agreed upon (without implementation details) in #3487484: Save page data form values in application state with support for undo/redo. Implementation was already done there, but moving into its own issue to reduce complexity for code reviews.

See MR description for proposed implementation details.

User interface changes

None.