feat(compiler-core): enhance the warning for v-once

[Bigfish8]

Close #4310
I think it is unnecessary to support this condition.But add compiler error will be helpful.

[yyx990803]

I don't even think this needs to be specifically about usage of scope variables. v-once isn't designed to be used inside v-for so the check and the warning message can both be simpler.

[Bigfish8]

I don't even think this needs to be specifically about usage of scope variables. v-once isn't designed to be used inside v-for so the check and the warning message can both be simpler.

Thanks for the review, I will simplify it.

[yyx990803]

Could you also add the same check for v-memo since they have the same limitations?

[Bigfish8]

Yes, I’ll be glad to.

[Bigfish8]

I changed the indentation of the previous test because of the separation between describe('transform') with describe('errors').So it seems there are many changes.

[edison1105]

Could you please resolve the conflicts?