revive llvm builder utility

[xermicus]

Pre-eliminary support for LLVM releases and resolc binary releases by streamlining the build process for all supported hosts platforms.

• Introduce the revive-llvm-builder crate with the revive-llvm builder utilty.
• Do not rely on the LLVM dependency in $PATH to decouple the system LLVM installation from the LLVM host dependency.
• Fix the emscripten build by decoupling the host and native LLVM dependencies. Thus allowing a single LLVM emscripten release that can be used on any host platform.
• An example Dockerfile building an alpine container with a fully statically linked resolc ELF binary.
• Remove the Debian builder utilities and workflow.
• Remove the vendored compiler-rt buitlins.

[smiasojed]

@xermicus it seems that you forgot to remove clone-llvm.sh or is it still needed somewhere?

There is an issue with llvm cache in WASM build - it does not work correctly. It seems like we would not cache the WASM llvm build:

 wasm-ld: warning: /home/runner/work/revive/revive/target/wasm32-unknown-emscripten/release/deps/liblld_sys-70cd6930db6dd32d.rlib: archive member 'AArch64ErrataFix.cpp.o' is neither Wasm object file nor LLVM bitcode
          wasm-ld: warning: /home/runner/work/revive/revive/target/wasm32-unknown-emscripten/release/deps/liblld_sys-70cd6930db6dd32d.rlib: archive member 'AArch64.cpp.o' is neither Wasm object file nor LLVM bitcode
          wasm-ld: warning: /home/runner/work/revive/revive/target/wasm32-unknown-emscripten/release/deps/liblld_sys-70cd6930db6dd32d.rlib: archive member 'AMDGPU.cpp.o' is neither Wasm object file nor LLVM bitcode
          ...

[xermicus]

@smiasojed thanks for pointing, made a follow up to fix it: #159