fix: fixes object literal parsing for <component :is>

[so1ve]

fix #3171

[so1ve]

@johnsoncodehk I think we should allow passing inline components since they just work well :( We should not pass an extra render prop to the component tag because it doesn't take effect and should be considered a bug.

[johnsoncodehk]

We need to avoid introducing additional conventions (__isFragment, __isTeleport, __isSuspense etc).
Perhaps we could append as any to ignore the type when the :is expression is an object literal.

[so1ve]

However, if we do so, type-checking will be disabled. I think my approach is fine, just need a new way to detect whether the argument is defined by using defineComponent.

[johnsoncodehk]

It cannot be perfectly supported, and if we decide to support object literals, we should also handle edge cases like :is="condition ? { render } : { props }".

Is your use case specific to the render option? If so, you can replace :is="{ render: eventSummary }" with :is="eventSummary", since functional component is a valid type.