Unable to alias Unstable_EffectOn type

[no-stack-dub-sack]

Similar to #634 and the issue described and fixed in #790, users of easy-peasy were unable to define their own aliases of the Action, Computed, and Thunk types. The same is true for Unstable_EffectOn, e.g.

type AppEffectOn<TModel extends object> = Unstable_EffectOn<
  TModel,
  StoreModel,
  Injections
>;

interface StoreModel {
  todos: TodosModel;
  rootData: number;
}

interface TodosModel {
  items: { id: number; text: string }[];
  foo: string;
  setFoo: Action<TodosModel, string>;
  onStateChanged: AppEffectOn<TodosModel>;
}

const todosModel: TodosModel = {
  // ...
  onStateChanged: unstable_effectOn(
    [
      (state) => state.items, // error! Property 'items' does not exist on type 'StateMapper<FilterActionTypes<{}>>'
      (state, storeState) => storeState.rootData, // error!
    ],
    (actions, change, helpers) => {
      actions.setFoo('bar'); // error! Property 'setFoo' does not exist on type 'Actions<{}>'
      helpers.dispatch.todos.setFoo('plop'); // error!
      helpers.getState().items[0].id + 2; // error!

      return () => console.log('dispose');
    },
  ),
};

Since the generic type params of the type are not actually used, TypeScript "forgets" them when the type is aliased. The fix should be straightforward which I can spin up a PR for shortly.