fix(Label, TextField test): resolve unit-tests and code-quality CI failures

- Prettier wants the Label component destructure on one line; reformat
  to match.
- The earlier `getAttribute('style')` assertion returned `null` when no
  style attribute was present, which `.not.toContain('color')` rejected.
  Use `element.style.color` instead, which returns `''` for "no inline
  color set" — the actual semantic we want to verify.

Author: DreaminDani

src/components/Label/Label.tsx

@@ -19,13 +19,7 @@ const labelVariants = cva(styles.label, {
   },
 });
 
-export const Label = ({
-  disabled,
-  error,
-  children,
-  className,
-  ...props
-}: LabelProps) => (
+export const Label = ({ disabled, error, children, className, ...props }: LabelProps) => (
   <label
     {...props}
     className={cn(labelVariants({ disabled, error }), className)}

src/components/TextField/TextField.test.tsx

@@ -44,8 +44,9 @@ describe('TextField', () => {
       // jsdom does not load. Visual parity is covered by the Playwright
       // suite at tests/display/label.spec.ts. The assertion below verifies
       // the InputWrapper does not inject a styled-components color override
-      // when no labelColor prop is passed.
-      expect(labelElement.getAttribute('style')).not.toContain('color');
+      // when no labelColor prop is passed (element.style.color is the empty
+      // string when no inline `color` is set).
+      expect(labelElement.style.color).toBe('');
     });
 
     it('is the color of the passed in labelColor', () => {