feat: use @vue/compiler-sfc as a compiler for TS if available

[cexbrayat]

Update: I'll let you decide but #5172 is probably a better alternative. See vuejs/vue-cli-plugin-vue-next#5 for more context

The fork-ts-checker-webpack-plugin is using vue-template-compiler by default, and this compiler is not the correct one to pick for vue-next. This commit tries to load @vue/compiler-sfc and falls back to vue-template-compiler if it does not find it.

It also bumps the fork-ts-checker-webpack-plugin to use v3.1.3

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Docs
• Underlying tools
• Other, please describe:

Does this PR introduce a breaking change? (check one)

• Yes
• No

Other information:

[haoqunjiang]

I think we can just add a file that shims the compiler API add pass it to the fork-ts-checker-webpack-plugin.

[haoqunjiang]

All it needs is a path to a file that exports the parseComponent API, which can be implemented by wrapping around the @vue/compiler-sfc public API.
https://github.com/TypeStrong/fork-ts-checker-webpack-plugin/blob/5008da9f4bd732bf70cfae0e187e4e4ecc95dfd1/src/VueProgram.ts#L303-L323

[cexbrayat]

@sodatea I updated the PR based on your idea.
To sum up:

• we need to use the latest fork-ts-checker-webpack-plugin to be able to give it another compiler (the one currently used does not)
• the second commit introduces a shim that just delegates to parse when parseComponent is called by the webpack plugin.
  I am open to suggestions for the file name and location.

We should now be able to remove vue-template-compiler from the devDependencies when using vue-next 🙂

[cexbrayat]

@sodatea I updated the PR with your feedback:

• now bumps to fork-ts-checker-webpack-plugin@3.1.1
• now uses require.resolve to load the new compiler