fix: resolve conflicts with vue2 interface

[MinatoHikari]

#850

Vue2 renderComponent Interface is different from vue3 now.

It works for me to resolve type error when I use Mixins in vue-class-component

Maybe we can change it's type again after vue2.7

[xiaoxiangmoe]

LGTM

[xiaoxiangmoe]

@MinatoHikari Can you add some type test for this in directory /test-dts?
If tests are added, the usage of vue-class-component and emit will not to be affected in future updates.
Thank you very much.

[MinatoHikari]

One problem, type checking in vsCode or webStorm is fine but vue-tsc will be failed when using vue3 tsconfig.
@antfu @xiaoxiangmoe

Because $emit in vue3's mounted instance dosen't return itself., so something like this.$emit('click', 1).$emit('click', 1) can not pass (using /vue3/dist/vue.d.ts), but it can pass with vue2 tsconfig.

[xiaoxiangmoe]

@MinatoHikari Maybe we can remove vue-class-component and vue-property-decorator in devDependencies. Only extract simpler use case from it.

[MinatoHikari]

Remove vue-class-component and vue-property-decorator.
Use case of #850 to simulate vue-class-component since I got same error when using vue-class-component.
To avoid conflicts when using vue3 type, move some tests to defineComponent-vue2.d.tsx, add exclude file for tsconfig.vue3.json.