refactor(label): convert enzyme tests to RTL

[nuria1110]

Proposed behaviour

Convert tests to RTL
Remove unreachable branch

Current behaviour

Tests are in enzyme

Checklist

• Commits follow our style guide
• Related issues linked in commit messages if required
• Screenshots are included in the PR if useful
• All themes are supported if required
• Unit tests added or updated if required
• Playwright automation tests added or updated if required
• Storybook added or updated if required
• Translations added or updated (including creating or amending translation keys table in storybook) if required
• Typescript d.ts file added or updated if required
• Related docs have been updated if required

QA

• Tested in provided StackBlitz sandbox/Storybook
• Add new Playwright test coverage if required
• Carbon implementation matches Design System/designs
• UI Tests GitHub check reviewed if required

Additional context

Testing instructions

[Parsium]

suggestion(non-blocking): how about this small wording tweak to better describe both the intended behaviour and the specific prop being tested?

Suggested change

	test("renders with provided `aria-label`", () => {
	test("uses `aria-label` prop as its accessible name when passed", () => {

[Parsium]

suggestion: what do you think of this modification to check the data-placement attribute on the tooltip? This would avoid the need to mock @floating-ui/react-dom:

Suggested change

	const user = userEvent.setup();
	const useFloatingSpy = jest.spyOn(floatingUi, "useFloating");
	render(
	<Label inline {...{ [validationProp]: "Message" }}>
	foo
	</Label>
	);
	await user.hover(screen.getByTestId(`icon-${validationProp}`));
	expect(useFloatingSpy).toHaveBeenCalledWith(
	expect.objectContaining({ placement: "top" })
	);
	useFloatingSpy.mockRestore();
	const user = userEvent.setup();
	render(
	<Label inline {...{ [validationProp]: "Message" }}>
	foo
	</Label>
	);
	await user.hover(screen.getByTestId(`icon-${validationProp}`));
	expect(await screen.findByRole("tooltip")).toHaveAttribute("data-placement", "top");

[Parsium]

suggestion: Similar to the previous test, what do you think about this change? It would avoid the need to mock @floating-ui/react-dom:

Suggested change

	const useFloatingSpy = jest.spyOn(floatingUi, "useFloating");
	render(<Label {...{ [validationProp]: "Message" }}>foo</Label>);
	await user.hover(screen.getByTestId(`icon-${validationProp}`));
	expect(useFloatingSpy).toHaveBeenCalledWith(
	expect.objectContaining({ placement: "right" })
	);
	useFloatingSpy.mockRestore();
	render(<Label {...{ [validationProp]: "Message" }}>foo</Label>);
	await user.hover(screen.getByTestId(`icon-${validationProp}`));
	expect(await screen.findByRole("tooltip")).toHaveAttribute("data-placement", "right");

[DipperTheDan]

Nothing more to add from me. Just address the comments left by @Parsium 😄

[carbonci]

🎉 This PR is included in version 142.9.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀