Support different query behavior on KtField*Select

[carsoli]

let's wait for future feature requests to decide on one of the following

1. adding an explicit attribute for searchValue on options - which is what the user can look for when querying
2. use one of those two "hacks" as a solution
   a) make the field "remote" and filter on the user app by more than just the option.label (aka by option.label || option.value
   b) make the label (since this is what the internal implementation uses know when the user queries) have the same value as the value and use the slot to show the label you want the user to see (e.g. { label: 'Label', value: 'Value' } --> becomes { label: 'Value', value: 'Value' } and the slot for option ACTUALLY shows 'Label'

Originally posted by @carsoli in #565 (comment)