fix(reactivity): chained computeds lost reactivity

[wanghanzhen]

When getting dirty and _dirtyLevel === DirtyLevels.MaybeDirty_ComputedSideEffect_Origin, it's supposed to execute resetTracking before return true. Otherwise, computed after that cannot be tracked and ends up losing reactivity.

Fix #11169

[Doctor-wu]

/ecosystem-ci run

[vue-bot]

📝 Ran ecosystem CI: Open

suite	result	latest scheduled
language-tools	✅ success	✅ success
nuxt	✅ success	✅ success
pinia	✅ success	✅ success
primevue	✅ 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

[wanghanzhen]

Hold on, just found a Maximum recursion error in my project after adding resetTracking😨
At present, the minimum reproduction has not been found yet.

[Doctor-wu]

@wanghanzhen could you try to provide reproduce, I think it's necessary to add resetTracking here to align behaviour with others dirty level

[wanghanzhen]

@Doctor-wu Finally got the reproduction. Here is the link:
https://play.vuejs.org/#eNp9UstOwzAQ/JWVL7SiSoFyoaSVAIEEB6iAoyWUJpuSktiWH6Eoyr+zdvpCoj0l2ZnZnd1Mw26UimqHbMxik+pCWTBonZpyUVRKagsNpLJSzmI2AI05tJBrWcEJiU644CKVwljIpYSJx3tn/etdeZ5oKm8a9Hp9mEyh4QK8IKqT0iGcTuCcJEBq67TYIVRs95ulB1qtdQ1kYz9w3bbdyeNhtxotFVusVJlYpHeAOCvqaUMbRhm0bTz0n4fr8XBPzAbMGvKVF4toaaSgAwYznHmLRYn6RdmCfHM27mx6LClL+f0UalY7HGzq6SemX//Ul2bla5zNNBrUNXK2xWyiF2g7+P7tGVf0vgUrmbmS2EfAVzSydN5jR7t1IiPbe7zg9jHEoBCLd3O/sijMZilv1DPbwOeMAnF3ZPWd3VE0Cjr6P3TFGWo6H92QLriN3OGgqUC/k07Yv4HDVdDmTqR++Jr4kKRW6p+eSCrsd2a6PnK+JP3anUfHoVnghYV8fvxzb+CBwFIrn7WQiY+a6DSelhlFl9HFFWt/ASbpIVA=

please confirm added resetTracking in source of devtools.

[Doctor-wu]

@Doctor-wu Finally got the reproduction. Here is the link: play.vuejs.org/#eNp9UstOwzAQ/JWVL7SiSoFyoaSVAIEEB6iAoyWUJpuSktiWH6Eoyr+zdvpCoj0l2ZnZnd1Mw26UimqHbMxik+pCWTBonZpyUVRKagsNpLJSzmI2AI05tJBrWcEJiU644CKVwljIpYSJx3tn/etdeZ5oKm8a9Hp9mEyh4QK8IKqT0iGcTuCcJEBq67TYIVRs95ulB1qtdQ1kYz9w3bbdyeNhtxotFVusVJlYpHeAOCvqaUMbRhm0bTz0n4fr8XBPzAbMGvKVF4toaaSgAwYznHmLRYn6RdmCfHM27mx6LClL+f0UalY7HGzq6SemX//Ul2bla5zNNBrUNXK2xWyiF2g7+P7tGVf0vgUrmbmS2EfAVzSydN5jR7t1IiPbe7zg9jHEoBCLd3O/sijMZilv1DPbwOeMAnF3ZPWd3VE0Cjr6P3TFGWo6H92QLriN3OGgqUC/k07Yv4HDVdDmTqR++Jr4kKRW6p+eSCrsd2a6PnK+JP3anUfHoVnghYV8fvxzb+CBwFIrn7WQiY+a6DSelhlFl9HFFWt/ASbpIVA=

please confirm added resetTracking in source of devtools.

@wanghanzhen It's occurred an error in 3.4.28 as well, could you commit a specific issue for this? I'll try to fix this and #11169 I'll commit the issue

[Doctor-wu]

@wanghanzhen Submitted #11183 for fixing both #11169 and #11181, reused your test case