[Enhancements] Ways to make OTA easier, user friendly and less problematic

I've seen sever challenges with the way OTA currently is. It's not easy to use and in some cases has literally caused problems that could have been easily avoided and/or far more easily fixed.

Suggestions to make the OTA system as nice to use as the rest of Z2M...

1. Manual point-n-click updates. Select a device (multi-select) -> Select a file from any location -> Upload/Update
   Currently we must jump through hoops to add info into the main config, create a new custom JSON file, then drop files into folders -- then hope the Z2M system properly recognizes the firmware for that device.... Why? This reminds me of how we did things in the late 90s (literally).

The current way creates a large problem if the firmware hoses anything in the versioning and model number... there is no way to easily force a firmware over the top to correct it (as happened with me in this issue

2. Provided needed information about the OTA files being used
   The Z2M system doesn't allow the user to know where the FW is coming from or what the file name is. So there is no way to know if what Z2M shows us as 'Available' is the FW from the local folder, or from the Internet; and where from the Internet (what actual file). As we've seen in this issue it can cause havoc if the OTA file Z2M sends you is bad. And because we dont have point-n-click updates (#1 above) it makes it difficult to reverse the damage the bad FW did.

3. Hide / Ignore Option
   There is no way to hide or ignore update notifications. In cases like custom FW or everything is stable and the users doesnt want a notification on 10, 20, 30+ devices they will never update... the OTA screen will always show an available version for no benefit.
   If the FW version Z2M presents from the Internet has a newer/larger version number than the local (in the local folder) firmware, it will always tell the users "this is newer" and present it to the user. In my case, I'll have 15 line items that always show and are not relevant since they will never need a FW update.

No files, tests, or entry points are named. First map the OTA screen and the current configuration, custom JSON, local-folder, and Internet firmware flows, then clarify which of the three proposals is in scope. Done requires agreed acceptance criteria for manual updates, firmware source and filename visibility, and hiding or ignoring notifications.