FunctionComponentOptions interface should allow model

[lazarljubenovic]

What problem does this feature solve?

It allows developers to use a functional way of declaring a component and utilizing the model config at the same time. It's already possible when using pure JavaScript.

What does the proposed API look like?

Add the missing part of the interface

  model?: {
    prop?: string;
    event?: string;
  };

to the existing interface FunctionalComponentOptions<Props = DefaultProps, PropDefs = PropsDefinition<Props>>.