For easy initial flashing. Flashing at address 0x0 with esptool.py
Generated in folder `.pio..../firmware-factory.bin` (Not used at the moment!)
## Checklist:
- [x] The pull request is done against the latest development branch
- [x] Only relevant files were touched
- [x] Only one feature/fix was added per PR and the code change compiles without warnings
- [x] The code change is tested and works with Tasmota core ESP8266 V.2.7.4.9
- [x] The code change is tested and works with Tasmota core ESP32 V.2.0.2
- [x] I accept the [CLA](https://github.com/arendst/Tasmota/blob/development/CONTRIBUTING.md#contributor-license-agreement-cla).
_NOTE: The code change must pass CI tests. **Your PR cannot be merged unless tests pass**_
#12837 @arendst @sillyfrog give it a try. I am a Python noob... The `map_name` generating is problematic. Better would be to use last entry of the string `src_dir`.
With the new toolchain used with IDF 4.4 the MAP file is in a different folder and the name has changed (from firmware.map to Tasmota.map).
Now name-firmware.py is searching for both-
When vscode is ran from the Tasmota folder in Linux, build fails with message :
```Executing task: pio run <
The terminal process failed to launch: Path to shell executable "pio" is not a file of a symlink.```
Renaming pio folder into pio-tools solve the problem.
Note: the problem can still occur if the user have a pio folder in his PATH...