fix: Missing ForwardRefExoticComponent and RefAttributes types in compat

[rschristian]

Fixes #3759, though only the immediate issue. Popper from @mui/material still does not type check correctly -- I added about a half-dozen types in compat and still couldn't get any type errors. We're missing a fair few things I guess, but that lib is such a maze of imports that I couldn't even track down all of what we were missing. Issue for another day I think?

Adapted from React's types here and here

---

To provide a simpler and more cut down reproduction than the original issue provided, the following example React library will generate the following types:

import { forwardRef } from 'react';

export const MyInput = forwardRef<HTMLInputElement, { label: string }>(function MyInput(props, ref) {
    return (
        <label>
            {props.label}
            <input ref={ref} />
        </label>
    );
});

export declare const MyInput: import("react").ForwardRefExoticComponent<{
    label: string;
} & import("react").RefAttributes<HTMLInputElement>>;

Aliasing react to preact/compat using "paths" in a tsconfig.json would convert the type of MyInput into any as ForwardRefExoticComponent and RefAttributes could not be found.

[coveralls]

Coverage: 99.707%. Remained the same when pulling a24d26b on types/compat-forward-ref-exotic-component into 19f4176 on master.

[robertmaier]

This is great :) I ran into the same problem integrating a React library today. Exchanging the types locally works as expected.

@JoviDeCroock Are there any plans to include this in one of the upcoming releases?

[JoviDeCroock]

@robertmaier people part of the org can merge their own PR's, I gave the green light by approving it but Ryan can merge himself when he feels like it :) it will then be part of a release later on.

Happy to hear the PR helps you!

[rschristian]

Whoops, totally forgot about this. Will merge in a minute.