build: fallback to autogen.sh if configure fails, and refactor config and build scripts for easier troubleshooting

[beorn]

Note to @addaleax - I am not very familiar with the node-gyp build system, and these changes do come with risks, so unless after your review you feel very confident in them, then I suggest we don't do these. It's perhaps better to tackle refactorings as part of a larger improvement effort on the build system for both windows and non-windows if/when that is done. Let me know if I should just close this PR.

---

This PR includes refactorings and some extra robustness if ./configure fails. It is arguably an improvement, but I'm not 100% sure removing the <! hack won't cause any problems (why was it there to begin with?).

For inspiration we could also look at node-ffi, which previously used a config and build script like we do, and:

1. include the unpacked source files, perhaps after re-running ./autogen.sh, so we don't need the config.sub patch
2. set up separate .gyp target for the libzma library

---

Changes:

• liblzma-config.sh: if configure fails, run autogen.sh / autoconf (*)
• Refactor build action in bindings.gyp so that config and build scripts output is shown, making troubleshooting easier:
  • It doesn't seem necessary to run configure using <! early variable expansion of 'input' key , so just run it as a regular build action, and make build dependent on it (in fact, they could be combined into one)
  • This means scripts can just output to stdout/stderr directly (instead of log files) for easier troubleshooting
  • Script output is made less verbose (but hopefully more clear)
• For reference, added link to actual XZ library used to README.md

(*) To run autogen.sh you need a full autoconf build environment to build, such as this shell.nix file defines if using Nix

{ pkgs ? import <nixpkgs> {} }:

pkgs.mkShell {
  buildInputs = [
    pkgs.darwin.cctools
    pkgs.python3
    pkgs.gettext
    pkgs.autoconf
    pkgs.automake
    pkgs.libtool
    pkgs.nodejs-17_x
    pkgs.p7zip # for yarn prepare-win
  ];
}

If encountering: gyp: name 'openssl_fips' is not defined while evaluating condition 'openssl_fips != ""' in binding.gyp while trying to load binding.gyp

Either wait for nodejs/node-gyp#2497 or update us node 17.