ESLint: Enable the method-signature-style rule

[acicovic]

Is your feature request related to a problem?

The TL;DR is that we should enable the https://typescript-eslint.io/rules/method-signature-style rule in our code, and fix any violations.

To see why, this is an example (originally quoted by @sirreal, can be found here):

type AnyItem = Record<string, any>;

interface Post extends AnyItem { status: string; }

type F<T> = (item: T) => boolean;
interface IF<T> { (item: T): boolean; }

interface Base<T extends AnyItem> {
  isEligible(item: T): boolean;
  isEligible1: F<T>;
  isEligible2: IF<T>;
}

const base: Base<AnyItem> = {
  // Why is this is OK?
  isEligible: (item: Post) => item.status.startsWith('eli:'),

  // These are both type errors as expected.
  isEligible1: (item: Post) => item.status.startsWith('eli:'),
  isEligible2: (item: Post) => item.status.startsWith('eli:'),
}

Relatedly: https://x.com/mattpocockuk/status/1803753059480121593

[sirreal]

I endorse this change 😀
The next version of wp-scripts will enable this in the recommended ruleset.

[acicovic]

Note to our future selves: As we aren't currently using the last version of wp-scripts due to WordPress/gutenberg#62202, we do want to add this rule, at least until we're able to upgrade.

[acicovic]

Related to #2624. If we become able to upgrade wp-scripts, then this rule will be auto-included. It probably makes sense to focus on #2624, as it should solve two issues at once.

[acicovic]

I finally went to fix this, since it was an easy win/change.