perf(reactivity): should not track __v_isRef and some methods in pr…

[underfin]

…ototype.eg.toString

Reproduction

 const App = {
    setup: () => {
      const data = reactive( {
        array: [1],
        object: {a: 1}
      } );

      return { data }
    },
    renderTracked(e) {
      console.log('key', e)
    },
    template: `
      <div  :literal="data.object" :obj="data.array.map((e) => e)"></div>
    `
  }

  let app = createApp(App);
  app.mount("#app");

Current Behavior

Changed Behavior

I'm not sure for this.I think it is helpful for better performance.If you agree with me, I will add some test for it.

[yyx990803]

This adds the cost of the hasOwn checks to every get access, which is likely even more expensive.

[yyx990803]

Multiple hasOwn checks are expensive, in addition, it's not entirely safe to skip these keys - for example, the user may add a new property named map to an object and this would cause it to not be tracked on the initial run when map is not on the object yet.