fix(reactiviy): fix arrays don't reactive when mutate index

[Doctor-wu]

Currently, mutating the array's index value won't trigger subscriptions, this PR fixes the tracking logic to prevent this problem. And I think we need to pass all eco-ci.
close #10455

[github-actions]

Size Report

Bundles

File	Size	Gzip	Brotli
runtime-dom.global.prod.js	90.6 kB (+37 B)	34.4 kB (+14 B)	31 kB (-2 B)
vue.global.prod.js	148 kB (+37 B)	53.7 kB (+14 B)	47.9 kB (-62 B)

Usages

Name	Size	Gzip	Brotli
createApp	50.8 kB (+37 B)	19.8 kB (+14 B)	18.1 kB (+27 B)
createSSRApp	54.1 kB (+37 B)	21.2 kB (+13 B)	19.3 kB (+20 B)
defineCustomElement	53.1 kB (+37 B)	20.6 kB (+16 B)	18.8 kB (+1 B)
overall	64.5 kB (+37 B)	24.9 kB (+13 B)	22.6 kB (-8 B)

[baiwusanyu-c]

/ecosystem-ci run

[vue-bot]

📝 Ran ecosystem CI: Open

suite	result	latest scheduled
language-tools	✅ success	✅ success
nuxt	✅ success	✅ success
pinia	✅ success	✅ success
quasar	✅ success	✅ success
radix-vue	✅ success	✅ success
router	✅ success	✅ success
test-utils	✅ success	✅ success
vant	✅ success	✅ success
vite-plugin-vue	✅ success	✅ success
vitepress	✅ success	✅ success
vue-i18n	✅ success	✅ success
vue-macros	✅ success	✅ success
vuetify	✅ success	✅ success
vueuse	✅ success	✅ success
vue-simple-compiler	✅ success	✅ success

[Doctor-wu]

@sodatea Hi, I don't think this PR just fixed the edge case, since case like this

const array = reactive([1, 2, 3])
watchSyncEffect(() => {
console.log(array.hasOwnProperty(0))
})
array[0] = 11

will not trigger reactive as well

[yyx990803]

The idea is right, but the fix can be placed in the instrumented hasOwnProperty returned by the proxy trap to only perform the string coercion only for hasOwnProperty, instead of all tracking calls. See c3c5dc9

Also the test case here doesn't actually test the problem in the original issue and passes even without the change.