feat(lint): implement noNestedComponentDefinitions rule

[mdevils]

Summary

Added the new rule noNestedComponentDefinitions,
which disallows nested component definitions in React components.

Closes #4989

This rule is useful for preventing potential performance issues and improving code readability by ensuring that components are defined at the top level.

Example (Invalid):

function ParentComponent() {
  function ChildComponent() {
    return <div>Hello</div>;
  }
  return <ChildComponent />;
}

Example (Valid):

function ChildComponent() {
  return <div>Hello</div>;
}
function ParentComponent() {
  return <ChildComponent />;
}

Test Plan

Tests are included.

[codspeed-hq]

CodSpeed Performance Report

Merging #6053 will not alter performance

_{Comparing mdevils:feat/no-nested-component-definitions (2784a0a) with main (a57a018)}

Summary

✅ 95 untouched benchmarks

[dyc3]

Great work, as always!

[dyc3]

Looks great!

Looking forward to the follow up PR, as discussed here: https://github.com/biomejs/biome/pull/6053/files#r2094610735

And, if you're looking for what to work on after that, I think you could take on #50.

[mdevils]

@dyc3 yep, I'll create a PR with react component detection improvements soon.

#50 is an interesting task, feel free to assign it to me.

[dyc3]

@mdevils I'll need you to comment on that issue for me to assign it. Github doesn't let you assign non-participants if they aren't a member of the org.