fix(types): Constrain Modifier Options to same type as Options in ModifierArguments

[eps1lon]

This targets 2.x.

Fixes issues with TypeScript 4.7 canary (microsoft/TypeScript#48366 specifically) that are blocking DefinitelyTyped/DefinitelyTyped#56210

Ran yarn build:typescript and made sure the same diff that fixed https://github.com/DefinitelyTyped/DefinitelyTyped/runs/5752176130?check_suite_focus=true#step:6:1271 was applied:

-export declare type Modifier<Name, Options> = {
+export declare type Modifier<Name, Options extends Obj> = {
     name: Name;
     enabled: boolean;
     phase: ModifierPhases;
     requires?: Array<string>;
     requiresIfExists?: Array<string>;
     fn: (arg0: ModifierArguments<Options>) => State | void;
     effect?: (arg0: ModifierArguments<Options>) => (() => void) | void;
     options?: Partial<Options>;
     data?: Obj;
 };

[rollingversions]

Change Log for @popperjs/core (2.11.4 → 2.11.5)

Bug Fixes

• Constrain Modifier Options to same type as Options in ModifierArguments

  Starting with Make the unconstrained type parameter and {} assignability rule not apply under strictNullChecks microsoft/TypeScript#48366
  TypeScript will not compile if type parameters don't have the same constraint. This change is required to type-check using TypeScript 4.7 canary

Edit changelog

[gaearon]

Hi @atomiks, sorry for direct ping but any chance you could have a look at this? This PR is currently the only thing blocking the release of the React 18 typings. Thank you <3

[gaearon]

Thank you! Appreciate that you’re taking a fix for 2.x.

[FezVrasta]

Thanks for the PR! The change is now live as @popperjs/core@2.11.5

[eps1lon]

Thanks for the PR! The change is now live as @popperjs/core@2.11.5

Awesome! Appreciate the quick action and really sorry you had to revive 2.x 😅