Make xtask work on Windows, add run-example command

[bjoernQ]

Since Windows is a little special there are various things where we need to do things in a special way.

Additionally, this adds the run-example command. That makes it easy to run an example without worrying about the features. We can also get nicer errors when trying to run something on an unsupported chip.

❯ cargo xtask run-example examples esp32s3 parl_io_tx
   Compiling xtask v0.0.0 (C:\projects\esp\esp-hal\xtask)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.09s
     Running `target\debug\xtask.exe run-example examples esp32s3 parl_io_tx`
[2024-02-28T12:31:01Z ERROR xtask] Example not found or unsupported for the given chip

[MabezDev]

Code looks good to me! Just a small nitpick on my side.

I do wonder if we want to unify (heh) how to run examples, like do we want to document that this is the way, or do we also allow users to cd into examples and get their hands dirty?

cc: @JurajSadel regarding documenting this

[MabezDev]

In the back of my head I'm wondering if this will cause issues down the line, but I don't have any real argument not to do this right now, I suppose we could always remove it if it does.

[jessebraham]

I can't really think of a situation where this would be problematic, we're in control of the Xtensa toolchain and this repository, so any changes made will be made by us. I think it's fine (at least for now).

[bjoernQ]

I do wonder if we want to unify (heh) how to run examples, like do we want to document that this is the way, or do we also allow users to cd into examples and get their hands dirty?

I'd say this could be what we tell users since they don't need to care about using the esp toolchain or which features to set. More experienced users probably will skip the README and just cd into the examples folder and run the examples manually (until they find out about the xtask)

[jessebraham]

LGTM, thanks for this! Sorry for always forgetting about Windows users 😁