auro-form: get auro-input working as an integrated form component

Is your feature request related to a problem? Please describe.

Auro form components, such as auro-input, auro-dropdown, etc., are currently self-contained individual repositories.

Due to this component independence, it has become challenging to maintain separate repositories with numerous interconnected dependencies, complicating the ability to validate a release across related parent components.

Describe the solution you'd like

Consolidate all Auro form components into a new auro-form component, reducing the distributed complexity of the Auro form library.

Acceptance Criteria

[x] Migrate auro-input into auro-form, beginning integration
[x] Update postCss.mjs to search directories recursively & process CSS files with PostCSS
[x] Update package.json scripts (such as sass:render) to search directories recursively
[x] Disable SCSS Stylelint rules (Components will be updated with latest markup upon release)
[x] Repo builds without error
[x] Bundler compiles as expected
[x] Confirm auro-form__bundled is generated, along with respective files for individual form components (auro-input__bundled, etc)
[x] Create Doc page that renders auro-dropdown and auro-input
[x] Migrate test files
[x] Migrate postscripts (postCss.mjs, etc) back to Auro Library for future component generation
[x] Investigate adding individual tests for components to package.json(exp: test:input)
[x] Investigate whether all nested components should be built using dev / build at once, individually or optionally.
[x] Update folder structure to incorporate new monorepo structure.
[x] #10
[x] #19
[x] #12
[ ] #21
[ ] #26
[x] #27
[x] #28
[x] #20
[ ] #14
[ ] #11
[ ] #30
[ ] #35

Additional context

No response

Exit criteria