fix: dropdown label value defaults

[TylerR909]

In BluePrint I find that this is very tedious...

<SelectField
  options={options}
  getOptionValue={(o) => o.id}
  getOptionLabel={(o) => o.name}
/>

...given that it's id/value or displayName/label/name/value seemingly 95% of the time. So, let's make getOptionValue/Label optional and try to infer, while still easily letting developers override or provide missing behavior when necessary.

Also, I tried to type-guard this (like if you pass in { code: string; id: string }[] it'd tell you getOptionLabel is required), but our abundant use of Interfaces over Types makes that a significant lift. Interfaces may only extend other Interfaces with statically-known types, so a key that's conditionally required or optional breaks extensions and a few overloads.

[stephenh]

Thought: Some of this should already be handled by the SelectField overload:

export function SelectField<O, V extends Value>(props: SelectFieldProps<O, V>): JSX.Element;
export function SelectField<O extends HasIdAndName<V>, V extends Value>(
  props: Optional<SelectFieldProps<O, V>, "getOptionValue" | "getOptionLabel">,
): JSX.Element;
export function SelectField<O, V extends Value>(
  props: Optional<SelectFieldProps<O, V>, "getOptionLabel" | "getOptionValue">,

I.e. it conditionally Optionalizes getOptionValue and getOptionLabel only when O has an id and name.

Granted, that was very inflexible, but it is more type-safe; can you try working the AtLeastOne trick as a replacement for O extends HasIdAndName, so that ideally we get both the increased flexibility of "use any one of these N fields" while not having to fallback on runtime checks for callers not passing the properties when they should?

(I had tried making this more flexible in the past, but didn't have the AtLeastOne trick, so it led to ~an egregious amount of overloads, like 1 overload per guessed label, 1 overload per guessed value, and so just gave up.)

[stephenh]

Thought: granted, this is not a public API, but would prefer using Value instead of any.

[stephenh]

Thought: Ideally these would be string ... or string | ReactNode?

[stephenh]

Suggestion: Surprised we don't have fail copy/pasted in, but seems worth it?