Update Electron version placeholder when adding local build

[nikwen]

Ideally, we should show the latest available version. But even updating it to a more recent version or a bogus version such as 0.0.0 would be useful.

[KhairyK]

Hello 👋,
I would like to take the opportunity to work on this issue.
At present, the Electron version placeholder does not reflect the actual version when using a local build, which may lead to confusion for users. My plan is to implement a solution that dynamically retrieves and displays the correct Electron version from the local build, effectively replacing the static placeholder.
I will create a dedicated branch for this enhancement and submit a pull request once I have thoroughly tested the changes to ensure both accuracy and stability.
Any guidance or recommendations regarding the preferred method for fetching the build version, or additional considerations, would be greatly appreciated.
Thank you for your time and attention, and I look forward to contributing.

[dsanders11]

I'm not sure this is really an issue - if anything we need to rethink how these version numbers are handled in general. Bad things happen if you give a local build the same name as an existing version, say v40.0.0. Maintainers tend to set their local build version to a high value like 999.0.0 to make it easy to find and avoid version conflict as new versions get released. This makes the Node.js typings not actually work, unfortunately. I think the concept in general is a bit broken and needs to be revisited.