Fixed Select components initial state.

[harrymaynard-maximus]

Please check if the PR fulfills these requirements:

• After these changes, the app was run and still works as expected
• Tests for these changes were added (if applicable)
• All existing unit tests were run and still pass

Please specify the type of change this PR introduces (Bug fix, feature addition, content update, chore, etc.):

Additional Notes:

[bryce-mcmath]

Looks good

[jlangy]

This looks great, just wondering what was breaking using the modelValue directly? Was it that it wasn't null by default? I've used that pattern in a couple of components so want to make sure it doesn't cause some hard to catch bug

[harrymaynard-maximus]

The issue was because the <select> element didn't use a v-model, it wouldn't bind the initial null value to the default option. And then there was an issue when selecting a valid option and then selecting the empty option, the empty option wasn't be selected. For some reason it use the option label value instead of the null value. That's why there's the additional logic in the change handler. This might only apply to <select> elements, but it could be worth double checking.

[stephanieharrison-maximus]

This all looks fine to me.

[jlangy]

Ah that makes sense. Looks like :value="null" does not act the way I expected, it leaves the value attribute off, which makes sense in hindsight. Looks like then the option falls back to its label if there is no value attribute. I'll make a note to check the DateInput and TimeInput, they use the same syntax. They may be alright since they have processing functions but will add some tests for toggling away and back to the default