fix(effect): computed lost reactivity

[Doctor-wu]

close #10114
This PR will re-introduce the problem of #10085, #10090, but the computed would not lose reactivity
I think this might be a trade-off in short term.

[github-actions]

Size Report

Bundles

File	Size	Gzip	Brotli
runtime-dom.global.prod.js	89.8 kB (+32 B)	34.2 kB (+2 B)	30.8 kB (-1 B)
vue.global.prod.js	147 kB (+32 B)	53.5 kB (+2 B)	47.8 kB (+46 B)

Usages

Name	Size	Gzip	Brotli
createApp	50.2 kB (+32 B)	19.6 kB (+2 B)	18 kB (+58 B)
createSSRApp	53.5 kB (+32 B)	21 kB (+3 B)	19.1 kB (-10 B)
defineCustomElement	52.5 kB (+32 B)	20.4 kB (+3 B)	18.6 kB (-11 B)
overall	63.9 kB (+32 B)	24.7 kB (+2 B)	22.4 kB (+41 B)

[Doctor-wu]

@yyx990803 @LinusBorg Could you help to invoke the ecosystem ci, to prevent this will cause some complex cases to fail

[yyx990803]

/ecosystem-ci run

[yyx990803]

Can you add a test case similar this this? nvm, the changed test case already does

[vue-bot]

📝 Ran ecosystem CI: Open

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

[yyx990803]

Looks like the quasar fail is a flaky transition test. Re-running to be sure.

[Doctor-wu]

The test seems to have passed, but the comment update failed😂