* simplify post_esp32.py
* make sure path has correct "\" or "/" regarding OS
* add os specific path separators
* more path possible issues corrections
* add function to normpath cmd
* set board_build.variants_dir = variants/tasmota correctly for OS
#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...
