Form wrapper

[mkernohanbc]

As we move towards shipping more data-input components (Select, TextField, TextArea, Button), we need to think about how users group several of these components together to build forms.

RAC includes a Form component that acts as a wrapper for multiple individual input components. It groups/associates a set of child inputs together semantically, and provides a parent object that can be targeted to configure styling, data validation and submission.

Form renders an HTML <form> element.

My current assumptions are:

• I think shipping a basic implementation of Form is a necessary counterpart to TextField, TextArea, Select and Button
• I think this component exists solely as a convenience/utility component in React library. It doesn't have a parallel in Figma
• Because Form is really just a semantic wrapper, I don't think has much in the way of visual styling by itself
• The key functions we need to document for users are how to target/style a form as a whole, and how to integrate it with their own business logic and handle data validation and submission

Going to do some initial investigation/prototyping, but will need @ty2k's read on the assumptions I'm making here and what the shape and role of this component could be.

[mkernohanbc]

POC component and Storybook story/docs are on this branch, as a conversation starter: https://github.com/bcgov/design-system/tree/398-form-wrapper