Fix typings for inferno-redux Provider component

[Seally]

Objective

This PR fixes some typing issues encountered when using inferno and inferno-redux in TypeScript environments.

The first fix fixes a typing issue that occurs when the root reducer function's second argument is not AnyAction. Previously Provider will reject any Redux Store<S, A> when A is not AnyAction unless it has been type casted as such. This fix was mostly copied from how @types/react-redux handles it.

The second fix fixes a type intersection issue caused by this interface

inferno/packages/inferno-redux/src/components/Provider.ts

Lines 16 to 19 in deccbe5

	export interface Props {
	store: Store<any>;
	children?: VNode | null | undefined;
	}

being passed here (aliased as P):

inferno/packages/inferno/src/core/component.ts

Lines 120 to 122 in deccbe5

	public props: {
	children?: InfernoNode;
	} & P;

This leads to the type of props.children to be:

VNode | (string & VNode) | (number & VNode) | (false & VNode) | (true & VNode) | (InfernoElement<any> & VNode) | (import("../../../inferno/src").InfernoNodeArray & VNode) | (JSX.Element & VNode) | null | undefined

Types like string & VNode and true & VNode is likely incorrect. I have been unable to determine why VNode was given as the type for Props['children'], but it seems to be an error and I've changed this to InfernoNode.

The last fix manually specifies the type of Provider#render() as a workaround for #1460. Without that line, TypeScript may infer the type and expand the InfernoNode type alias during .d.ts generation, leading to an incorrect in-place import for InfernoNodeArray to be generated.

Closes Issue

It closes Issue #1460.

[coveralls]

Coverage remained the same at 95.059% when pulling cdc0382 on Seally:provider-type-fix into deccbe5 on infernojs:master.

[Havunen]

Hi @Seally

Changes looks good to me. Can you add some way to test the issue this fixes please :-)

It could be done for example by creating tsx test file to render something

[Havunen]

Thank you @Seally