fix(select): revert commit to fix skipping over blank disabled options

An earlier commit caused an error where the first option of a select would be skipped
over if it had a blank value. This fix adds a test case to identify this case and shows
that reverting the earlier commit causes the behavior to change.

Relates to #7715
I'm not really sold on that approach.

Previously, we were doing this work in the watch expression, and knew specifically which options changed and how.

Now, we're deep-watching with the same watch action twice, without knowing what's changed and what hasn't. For small collections of options it won' t matter, so if we're shipping this, really emphasize that it's not intended for large collections or complex collections of options