Refactor: Replace @HostBinding with host property of Component Decorator

[elite-benni]

PR Checklist

Please check if your PR fulfills the following requirements:

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

PR Type

What kind of change does this PR introduce?

• Bugfix
• 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
• hover-card
• input
• label
• menubar
• navigation-menu
• popover
• progress
• radio-group
• scroll-area
• select
• separator
• sheet
• skeleton
• slider
• switch
• table
• tabs
• textarea
• toast
• toggle
• tooltip
• typography

What is the current behavior?

The Binding of the Class is set to Host with a @HostBinding, which is not the preverred approach as stated in angular.dev.
@HostBinding also does not work with onPush Parent Components and changes to the property.

Closes #

What is the new behavior?

The classes are bound to the host property of the component decorator.
Signals or computed that are bound via host property also work with changes.

Does this PR introduce a breaking change?

• Yes
• No

Other information

I also implemented the userCls signal in every Component with the same structure, so we should not have a too hard time when migrating to signal based inputs.
closes #55

[vercel]

Someone is attempting to deploy a commit to a Personal Account owned by @goetzrobin on Vercel.

@goetzrobin first needs to authorize it.

[goetzrobin]

Looks good to me! There is a tiny conflict after merging a different PR, once you fix that one I will merge it!

[goetzrobin]

@elite-benni Thank you! That was fast!
Noticed another minor thing: Can we make all the signals readonly. Just to add a layer of "security" as signals are not meant to be reassigned. Another mess I am trying to clean up lol

[nartc]

LGTM. Though I have a non-blocking question, some places still use generateClasses() private method while some other places don't. Can we make this more consistent?

[elite-benni]

Sure, I can do this.
The generateClasses() that are left are because it was easier to replace the old code.

The whole idea of this change was to make it more consistent. Thanks for pointing that out.
I think keeping generateClasses everywhere, is easier to read.

I will add readonly to the signals.

[goetzrobin]

Btw you can run yarn prettify to format the files for you before committing since you are touching a good amount of them with this PR :)

[elite-benni]

I merged the conflict in github. ;) thats why i missed the empty line ;)

[goetzrobin]

🚀 Thanks for making those changes!