fix(runtime-dom): When the prop of a custom element is undefined, the property should be deleted

[linzhe141]

close #11276

[github-actions]

Size Report

Bundles

File	Size	Gzip	Brotli
runtime-dom.global.prod.js	89.4 kB (+34 B)	34.2 kB (+11 B)	30.8 kB (+26 B)
vue.global.prod.js	146 kB (+34 B)	53.6 kB (+9 B)	47.7 kB (+46 B)

Usages

Name	Size	Gzip	Brotli
createApp	51.3 kB	20.1 kB	18.3 kB
createSSRApp	54.7 kB	21.4 kB	19.5 kB
defineCustomElement	53.6 kB (+34 B)	20.9 kB (+10 B)	19 kB (-9 B)
overall	65 kB	25.1 kB	22.7 kB

[Maxim-Mazurok]

Might be a good idea to add some tests to avoid regression in the future

[Maxim-Mazurok]

Tests are looking awesome 👍

I wonder: will this new logic affect any use-cases where someone would try to pass undefined as a prop value? Or if they omit the prop. Will it make it false where undefined was expected previously? Basically don't want to be too selfish with only solving my use-case with Boolean prop, maybe should think about other cases as well. On other hand I'd expect some tests to fail if that was the problem, so maybe we're good...

[so1ve]

/ecosystem-ci run

[vue-bot]

📝 Ran ecosystem CI: Open

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

[edison1105]

Closing as #11276 has been fixed via 506c4c5