Name Attr for QSelect on null modelValue

[ahmedjas1m]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Documentation
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes
• No

The PR fulfills these requirements:

• It's submitted to the dev branch (or v[X] branch)
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• It's been tested on a Cordova (iOS, Android) app
• It's been tested on an Electron app
• Any necessary documentation has been added or updated in the docs or explained in the PR's description.

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to start a new feature discussion first and wait for approval before working on it)

Other information:

We've just tried to solve a bug that developer might face which already happened and mentioned in this issue.

QSelect doesnt add name attr for select element in the dom when the modelValue for Qselect is null. It's due to the checking statement for inner options lengths in QSelect while adding the name attr.

thanks to the issue reporter @cmcleese

[github-actions]

UI Tests Results

    1 files     98 suites   39s ⏱️
1 031 tests 1 031 ✅ 0 💤 0 ❌
1 050 runs  1 050 ✅ 0 💤 0 ❌

Results for commit ce9e51d.

[cmcleese]

from the looks of the PR, i'd its correct