Add option to make `resholve.writeScript` run the same checks that `writeShellApplication` does

[Jayman2000]

When you call pkgs.writeShellApplication, it checks your script using shellcheck and bash -n. It would be nice if resholve.writeScript and resholve.writeScriptBin did the same thing.

[abathur]

I recently removed the bash -n support because it was causing cross issues reported up in nixpkgs.

I wasn't feeling terribly clever at the time, but IIRC the main reason I removed it when I looked into a fix is that these core writers are leaning on stdenv magic (stdenv.shell via stdenv.shellDryRun) to get a runnable shell for the checkPhase.

This isn't as straightforward for the resholve api since it enables us to specify the interpreter.

I'm okay with re-treading this ground and added a test in the flake (

resholve/flake.nix

Line 171 in 685c25a

aarch64-cross-test_writeScriptBin =

) to make it easier to revisit without regressing, but I also don't want to carry meaningful complexity for doing this just in resholve's case if that makes sense.

(Maybe I have missed something that exists, but if not I think it makes more sense to figure out what generalization or abstraction is missing in nixpkgs to handle this for more use cases?)