Remove setState usage in componentDidMount for Menu popover

Description

The PopoverMenuWrapper component in the Livechat Menu uses setState inside componentDidMount, with an explicit eslint disable:

// eslint-disable-next-line react/no-did-mount-set-state
this.setState({
    position: { left, right, top, bottom },
    placement,
});

Calling setState in componentDidMount is a known React anti-pattern and introduces an extra render cycle. The eslint disable suggests this is acknowledged technical debt.

Proposed Solution

Refactor PopoverMenuWrapper from a class component to a functional component and replace the lifecycle logic with useLayoutEffect, which is more appropriate for synchronous DOM measurements.

Key points:

• Use useLayoutEffect for layout-dependent calculations
• Preserve existing behavior and public API
• Remove the eslint disable comment
• Keep the ref typed as HTMLDivElement

Expected Impact

• Eliminates a React anti-pattern
• Removes lint suppression
• Aligns with the project’s ongoing migration toward functional components
• No behavioral or visual changes

Notes

I can open a PR with this refactor.

Locate the TypeScript PopoverMenuWrapper component in the Livechat Menu and read its componentDidMount logic, ref handling, and public API. Refactor the layout measurement while preserving behavior, remove the eslint disable, and verify that linting and existing component checks pass without visual changes.