fix: regression in no-unstable-context-value in 1.29.0

[mrginglymus]

No actual fix, but a repro demonstrating the issue.

{
    ruleId: '@rule-tester/no-unstable-context-value',
    severity: 2,
    message: "A/an 'arrow function expression' passed as the value prop to the context provider should not be constructed. It will change on every render. Consider wrapping it in a useCallback hook.",
    line: 2,
    column: 24,
    nodeType: 'ArrowFunctionExpression',
    messageId: 'unstableContextValue',
    endLine: 4,
    endColumn: 8
  }

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue #___
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• I have added a convincing reason for adding this feature, if necessary

Other information

[vercel]

@mrginglymus is attempting to deploy a commit to the Rel1cx's projects Team on Vercel.

A member of the Team first needs to authorize it.

[mrginglymus]

Looking at the blame, seems like not a regression in no-unstable-context-value, but an existing bug now exposed by better heuristics for identifying context providers.

[mrginglymus]

Thanks for the quick fix @Rel1cx!