Fix malformed user input error on MJPEG config flow

[codyc1515]

Proposed change

Name is required for the config flow but doesn't make it mandatory - this change does - which fixes error "User input malformed: expected str for dictionary value @ data['name']".

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the [development checklist][dev-checklist]
• I have followed the [perfect PR recommendations][perfect-pr]
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

[frenck]

Thanks, @codyc1515 👍

../Frenck

[MartinHjelmare]

Shouldn't we fix the default instead so that it's never None?

Also, we should not use dict.get on line 157 since we know that the key will exist in the dict.

[codyc1515]

Agree. This change was the simplest way I could see to "fix" the issue without risking breaking something else.

I don't understand why the name is ever asked for, which is the real reason this issue ever existed. It's asked once on setup then can never be configured again.

To be honest, I also don’t understand why the MJPEG variant of Generic Camera exists at all - shouldn't MJPEG cameras simply work in the Generic Camera?