refactor: vue update by hmr api

[underfin]

I do it because i think it is useful for let the logics with built-in vue process can be as an plugin.Well I think the hmr with vue module should be implement by hmr api, instead of use internal logic

Other

I find top boundary will update self when deps is changed.eg blew case.

hot.accpet('A',  'B', () => {} )

I think this bevaior should be handle by user self.vite don't do it because sometimes user don't hope A full-reload when B change.
If the user want to do this bevaior.they can do like this blew.

hot.accpet('A',  'B', () => {
   import('A') // re-import A
} )

Or better way. we can add hmr bubble for not accpet deps.And accpet deps should not bubble.Like this blew.

// A
import 'B'
import 'C'
hot.accpet('A',  'B', () => {} )

A should not update when B changed.A should update when C change.

[yyx990803]

This is actually an intentional fix because self-accepting callbacks should be called when a dep change bubbles up to the boundary. (e.g. #207)

[yyx990803]

Removal of the check is intentional. This should be reverted.

[yyx990803]

Also let's avoid mixing unrelated changes in the same PR.

[underfin]

Copy that.
But I change it becasue any change will bubbles up to the boundary when i use hmr api for refactor vue file hmr.That will cause hmr don‘t minimize update for vue file.And also maybe the pr is unnessary.

[underfin]

I revert this hmr change already.we can just do it with current hmr api.

[yyx990803]

I think something is going on with appveyor, the fails seem unrelated.