Button component configuration code should align with design documentation and pattern library
Problem
The way a button is currently configurable code-wise in the application is not aligned with how we have documented it and discuss it. Removing this matrix needed to get the same result as intended into the application will remove friction in terms of developer hand-off and will bring transparency for cross-functional involvement to the future development of in this case the button component.
Proposal
Each button type, style, variation, and sizing should be configurable as such from within the <gl-button>
or dedicated component with the same terminology.