fix(types): make VNodeChildrenArrayContents type more accurate

[ktsn]

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

• Bugfix
• Feature
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

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

• Yes
• No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
• New/updated tests are included

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

• Replaced VNodeChildren with VNodeChildrenArrayContents in its recursive declaration. The current VNodeChildrenArrayContents type looks inaccurate because it can include a scoped slot in the returned value of another scoped slot.
• VNodeChildrenArrayContents inherits Array interface so that we can narrow the type with Array.isArray function.

[HerringtonDarkholme]

I wonder where is [ScopedSlot] used. VNodeChildren is used in createElement function. But it seems scopedSlots should be defined in another argument rather than VNodeChildren. https://vuejs.org/v2/guide/render-function.html#createElement-Arguments

[HerringtonDarkholme]

Ok I found it
https://github.com/vuejs/vue/blob/dev/src/core/vdom/create-element.js#L81-L83