types: allow ExtractPropTypes to make props with default values optional

[HcySunYang]

close: #3122

[HcySunYang]

CI failure is irrelevant

[07akioni]

#3122 (comment)

[HcySunYang]

I read the comments, but this PR did not introduce any breaking changes, it just allows the user to do it with the way they want, just a utility for types

[07akioni]

It may cause breaking changes.

{
  props: {
    foo: {
      type: Object as PropType<{ key: string }>,
      default: () => ({ key: 'bar' })
    }
  },
  setup (props) {
    function f (x: string) {}
    // If props.foo is optional, then break
    f(props.foo.key)
  }
}

I think if you did want do this, distinguish resolved (inside setup) & passed (from render function) version ExtractPropTypes is needed.

[HcySunYang]

@07akioni did not break that, you should notice that MakeDefaultsOptional is false by default, which is the original behavior

[Eterion]

Is it really the best course of action to extend the ExtractPropTypes with a parameter, instead of creating new type for it?
I'm concerned about the final readability in the code, for example:

const useProps: ExtractPropTypes<typeof props, true> = {}

It's not really obvious what the second parameter actually does. I would rather see a new standalone type for it (doesn't have to be named like this).

const useProps: ExtractUsagePropTypes<typeof props> = {}