Use reponse file on windows and when using gcc

[N3xed]

This is to circumvent the command-line length limitation on windows.

Export shlex::join as join_unix_args
Export shlex::quote as quote_unix_arg
Change LinkArgsBuilder::build to return a Result<LinkArgs>
Add cargo::out_dir

[ivmarkov]

Looks OK, I'll merge. BTW, these changes probably fall within the perhaps-not-necessary-to-peer-review category, as the API changes are minimal and the rest is Windows specific stuff we have to address anyway.

(Edit: I've submitted a separate issue for the problem below)
Related:
I am half there in figuring out the linkage problems with the native build and the C3 chip:

• Rust is spitting out a -nodefaultlibs option on the command line, which seems to be kind of like "the default behavior" (but it seems you can control this on a Rust target level, when you define the target)
• This is somehow preventing the linker from finding the missing intrinsic (__trunctfdf2); if I remove the -nodefaultlibs, it works OK
• Short term solution: we have a simple workaround in adding a rustflags = ["-C", "default-linker-libraries"] to the [target.riscv32imc-esp-espidf] section in .cargo/config.toml in the relevant binary crate (rust-esp32-std-hello etcetera)
• Long term solution: we should probably allow the "default libs" behavior on the Rust target level (as in riscv32imc-esp-espidf as well as in all xtensa targets, if it is not allowed there). Reason why I believe this is a correct behavior: I don't see the -nodefaultlibs argument amongst the "native" (cmake) args, which means the native ESP-IDF build is assuming it is NOT set

Unresolved questions/issues:

• Why is this argument defined in the first place? The Rust/cargo committers are fuzzy on the topic:
  • Option to disable -nodefaultlibs to the linker rust-lang/rust#54237
  • alexcrichton/rust@6f4b378#diff-7ece3daa669e665894c845baaf8c173af652c56ad5306e18c74504f9df2577faR1141
• Why does the build work for the Xtensa targets? Either they opt out from the -nodefaultlibs option, or that particular intrinsic is simply not needed on Xtensa. Not sure
• Why does the ESP32C3 build work via PlatformIO? Superstrange.