Re-add target option to zwave-js firmware upload

[raman325]

Proposed change

This PR was a mistake: #15425

We should have never removed this option but I misunderstood the implications of a new zwave-js release and learned about this issue recently so it's been readded everywhere else upstream, including in core here: home-assistant/core#88523

I made some slight modifications to the things I removed in the original PR. Mainly I changed the intro text because it was not accurate, and the target is now undefined by default. This means that if the user doesn't make a change, we send undefined upstream to the zwave-js-server and let zwave-js decide how to handle it.

Type of change

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

Example configuration

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io