Treat curried custom HOC calls as components in only-export-components rule

[Copilot]

Styled-components’ object-call form and other curried HOCs were still flagged as non-components. E.g.:

export const Flex = styled("div")({ display: "flex" }); // wrongly warned

• Detection: Traverse chained HOC callees with depth guard; treat curried HOC call expressions as components while still requiring arguments.
• Consistency: Reuse HOC detection for variable initializers so curried custom HOCs count as React components.
• Regression tests: Added coverage for styled('div')({ ... }) in named and default exports when listed in customHOCs.

Example:

export const Flex = styled("div")({ display: "flex" }); // now accepted with customHOCs: ["styled"]

Original prompt

Hi, the template-literal form of styled components seems to have been fixed ArnaudBarre#32, but the object form still causes false positives:

export const Flex = styled('div')({display: 'flex'}) // Warning ❌

We can get halfway there with "customHOCs": ["styled"]

export const Flex = styled('div') // No warning ✅
export const Flex = styled('div')({display: 'flex'}) // Warning ❌

For the purposes of this plugin, I think it would be safe to assume that if you call the result of a "HOC", it should count as a react component.

I believe the correct term for a function like this case of styled is a curried HOC.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.