feature(form-field) create new component to handle errors and hints

[cjosue15]

PR Checklist

Please check if your PR fulfills the following requirements:

• [x] The commit message follows our guidelines: https://github.com/goetzrobin/spartan/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• [x] Tests for the changes have been added (for bug fixes / features)
• [x] Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• [ ] Bugfix
• [x] Feature
• [ ] Code style update (formatting, local variables)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] CI related changes
• [ ] Documentation content changes
• [ ] Other... Please describe:

Which package are you modifying?

• [ ] accordion
• [ ] alert
• [ ] alert-dialog
• [ ] aspect-ratio
• [ ] avatar
• [ ] badge
• [ ] button
• [ ] calendar
• [ ] card
• [ ] checkbox
• [ ] collapsible
• [ ] combobox
• [ ] command
• [ ] context-menu
• [ ] data-table
• [ ] date-picker
• [ ] dialog
• [ ] dropdown-menu
• [x] form-field
• [ ] hover-card
• [ ] icon
• [ ] input
• [ ] label
• [ ] menubar
• [ ] navigation-menu
• [ ] pagination
• [ ] popover
• [ ] progress
• [ ] radio-group
• [ ] scroll-area
• [ ] select
• [ ] separator
• [ ] sheet
• [ ] skeleton
• [ ] slider
• [ ] sonner
• [ ] spinner
• [ ] switch
• [ ] table
• [ ] tabs
• [ ] textarea
• [ ] toast
• [ ] toggle
• [ ] tooltip
• [ ] typography

What is the current behavior?

None

Closes #294

What is the new behavior?

Create a new component to handle errors and hints like the material functionality but with the shadcn styles.

Does this PR introduce a breaking change?

• [ ] Yes
• [x] No

Other information

[cjosue15]

I added some comments! I really like the idea of this and the overall approach seems fine to me, too. One big question I have: Is there a way to support this with uncontrolled form controls, too? e.g. just add a (host) directive to any form control that's Angular form compatible and automatically get the functionality, instead of having to manually update the form state on every doCheck

Thanks for review it, when you say uncontrolled form controls, you mean inputs or selects without any of these (FormControl or formcontrolName). Also I think it is not possible to use this validation as HostDirective because only some components must have the errorState, another point is each component that will be used inside the FormFIeld component should be use the BrnFormFieldControl in the providers, to be identified by the parent(form-field), additionally using the update of the error in the ngDoCheck is the only way, at least that I know of, where I can reevaluate on every change detection when the error is triggered.