Form Label - Ensure Consistency between Storybook Documentation and Codebase Property Names

[angelicahoyss]

Description / User Story

As a developer on the team,
I want to ensure consistency between the property names defined in the Storybook documentation for Form Label component
So that the Form Label component codebase accurately reflects the documented property names.

This user story outlines the need to maintain consistency between the documentation and the codebase regarding component property names. Each component is checked to ensure the property names in the codebase match the corresponding names in the Storybook documentation. If the discrepancies are found, they are listed in this table on the page "FormLabel",. Column Current Code Property Name describes how is the property currently named in the code. Column Desired Code Property Name is how the property should be named. Properties marked green don't need adjustment.

---

Acceptance Criteria

• All Form Label component's property names that differ from Storybook documentation property names (listed in the above mentioned table) should be updated
• Property 'variant' should be renamed to 'hasError' and re-written as a boolean type instead of LabelVariantType
• The updated property names should not introduce any unintended side effects or issues in the functionality of the components
• The library builds successfully, and there are no reported issues related to the property name updates
• Props Excel has been updated / comments have been resolved and props changed from red to black font color > @thrbnhrtmnn or @angelicahoyss can support here

[thrbnhrtmnn]

Hey @RubirajAccenture , I saw one issue on develop. Could you change the "hasError" prop, so that it is a boolean in Storybook? I think this is also how the property behaves in the component and it would also be more consistent with other hasError props, if it is a boolean here and if users turn this to "true", the error state is displayed.