Could https://web.esphome.io/ be made to create a generic firmware with a generated hostname, ready for homeassistant 'adoption'?

**Describe the problem you have/What new integration you would like**
I recently used https://web.esphome.io/ to flash a generic ESP32 USB board, which worked great. I was really impressed how it then magically appeared in ESPHome web gui ready for adoption, without first creating a yaml file.

However, this doesn't work with something like Tuya-convert, which needs you to flash the firmware first - and that means creating a device/yaml with a set hostname. If you're flashing lots of devices, it would be great to just get them into an 'adoption' state, with a generic hostname you can set at the time of adoption. You could then just flash a bunch of them, and they'd all appear ready to be adopted and flashed OTA.

**Please describe your use case for this integration and alternatives you've tried:**

Creating a yaml first and then uploading the firmware works fine. It's just a pain when flashing a dozen plugs.

**Additional context**

Not really - except to say thank you. Amazing how far this project has come!

The payload names https://web.esphome.io/ and the Home Assistant adoption flow but no repository files, tests, or entry points. Start by locating the web flasher's generic-firmware and adoption handling, then verify that freshly flashed devices can receive generated hostnames and appear ready for adoption.

Written by the indexing model from the issue text.