[Fix] boolean-prop-naming: detect TS interfaces

[developer-bandi]

related to #3285

in this issue I found four error case. The test case is below:

interface Props {
  enabled: boolean
}
const Hello = (props: Props) => <div />;

const Hello = (props: {enabled:boolean}) => <div />;

type Props = {
  enabled: boolean
}
const Hello = (props: Props & BaseProps) => <div />;

type Props = {
  enabled: boolean
}
const Hello: React.FC<Props> = (props) => <div />;

Currently, PR is working on the first case fix that corrects the interface error, which is the main content raised in the issue.

I think the code needs to be modified so that all test cases succeed, but it seems like there is many cases to work on at once in this PR, so I am wondering whether this should be done in one PR, or if it can be done in a different PR for each test case.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.75%. Comparing base (8c2bdb2) to head (8436cf6).

❗ Current head 8436cf6 differs from pull request most recent head 901c794. Consider uploading reports for the commit 901c794 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #3701   +/-   ##
=======================================
  Coverage   97.75%   97.75%           
=======================================
  Files         133      133           
  Lines        9462     9464    +2     
  Branches     3466     3466           
=======================================
+ Hits         9250     9252    +2     
  Misses        212      212           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ljharb]

Thanks, seems straightforward!