[Bug Report][3.10.5] VInput v-slot provided values shouldnt be too reactive

[FragsterAt]

Environment

Vuetify Version: 3.10.5
Vue Version: 3.5.22
OS: Windows 10 (current)

Steps to reproduce

1. open reproduction URL
2. first input state isnt erroneousб because scoped value is nested reactive
3. second input is using .value in template (sic!)
4. third and fourth inputs cast all to boolean via toValue

Expected Behavior

direct check of scoped value, like in third and fourth inputs

Actual Behavior

isValid.value is ComputedRef, so I need to use .value in template

Reproduction Link

https://play.vuetifyjs.com/#...

Images

[FragsterAt]

vuetify/packages/vuetify/src/components/VInput/VInput.tsx

Line 149 in c20031b

const slotProps = computed<VInputSlot>(() => ({

instead of

    const slotProps = computed<VInputSlot>(() => ({
      id,
      messagesId,
      isDirty,
      isDisabled,
      isReadonly,
      isPristine,
      isValid,
      isValidating,
      hasDetails,
      reset,
      resetValidation,
      validate,
    }))

should be

    const slotProps = computed<VInputSlot>(() => toValue({
      id,
      messagesId,
      isDirty,
      isDisabled,
      isReadonly,
      isPristine,
      isValid,
      isValidating,
      hasDetails,
      reset,
      resetValidation,
      validate,
    }))

to remove excess reactivity, but it may be a breaking change, so I didn't make pr yet

IMHO the same changes should be made in other components with scoped slots too