fix(reactivity): accept subtypes of collections

[unbyte]

Fixed usage scenarios using subtypes of collections:

  class CustomMap extends Map {
    get(key) {
      console.log(key)
      return super.get(key)
    }
  }

  class SMap extends CustomMap {
    set(key, value) {
      console.log(key, value) // or other actions
      return super.set(key, value)
    }
  }

  const a = reactive(new SMap())

  a.set('a', 'ok')

// Error:  TypeError: Method Map.prototype.set called on incompatible receiver [object Object] 

close #1868

[unbyte]

@Picknight I think it's a better solution than #1799

[Picknight]

@Picknight I think it's a better solution than #1799

Yep, I think this one is better.

btw, this PR essentially replaces the type judgment basis from target.constructor to toRawType(target), I'm not sure if there is a potential problem.

[unbyte]

Yep, I think this one is better.

btw, this PR essentially replaces the type judgment basis from target.constructor to toRawType(target), I'm not sure if there is a potential problem.

I've found this as a reference http://perfectionkills.com/instanceof-considered-harmful-or-how-to-write-a-robust-isarray/

[unbyte]

using switch instead of map and object is based on this benchmark
https://jsben.ch/Pt9NS

[yyx990803]

I like this one, thanks for iterating on this!