As I mention in #622 (comment), this MR adds validation of args, kwargs, slots, and data (returned from get_context_data) based on the types passed to the Component's generics.

The reason I wanted to add this is following:

When I was adding the typing support to the components, I had two options:

1. Either use ParamSpec as one of the Component's generics, which would be bound to the get_context_data. This way, the get_context_data function would have been the source of truth for the type.
2. Or define args and kwargs as I eventually did, as a Tuple and TypedDict. This way, the Component.render would still be correctly typed, but the signature of get_context_data could diverge.

I went with option 2, because even I haven't worked with ParamSpec before, and I didn't want to ask users to pass around something which they might have never used before. It seemed complex. On the other hand, defining just tuples and typed dicts seems a lot more intuitive.

But that means that one could add typing for the Component, and the args and kwargs declared in the types could be totally different from the actual implementation of get_context_data.

So this MR adds some guard rails so that the component's implementation must be compatible with the declared args and kwargs types.

Altho, this is applicable only for Python 3.11 and later. In older versions, args are still validated, but TypedDicts like kwargs, slots, and data, are typed only, but not validated.