Missing development environment setup info for cargo-spellcheck

[sandersaares]

While we are in general missing a development environment setup guide and related scripting/tooling, for the most part it can be figured out on the fly (e.g. taking GitHub workflows as reference). However, cargo spellcheck appears not to be so easy to setup:

cargo install cargo-spellcheck

results in

warning: clang-sys@1.8.1: could not execute `llvm-config` one or more times, if the LLVM_CONFIG_PATH environment variable is set to a full path to valid `llvm-config` executable it will be used to try to find an instance of `libclang` on your system: "couldn't execute `llvm-config --prefix` (path=llvm-config) (error: program not found)"
error: failed to run custom build command for `clang-sys v1.8.1`

Caused by:
  process didn't exit successfully: `C:\Users\sasaares\AppData\Local\Temp\cargo-install1PHDae\release\build\clang-sys-2147579cc6ebb833\build-script-build` (exit code: 101)
  --- stdout
  cargo:warning=could not execute `llvm-config` one or more times, if the LLVM_CONFIG_PATH environment variable is set to a full path to valid `llvm-config` executable it will be used to try to find an instance of `libclang` on your system: "couldn't execute `llvm-config --prefix` (path=llvm-config) (error: program not found)"

  --- stderr

  thread 'main' (94696) panicked at C:\Users\sasaares\.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\clang-sys-1.8.1\build\dynamic.rs:225:45:       
  called `Result::unwrap()` on an `Err` value: "couldn't find any valid shared libraries matching: ['clang.dll', 'libclang.dll'], set the `LIBCLANG_PATH` environment variable to a path where one of these files can be found (invalid: [])"
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to compile `cargo-spellcheck v0.15.5`, intermediate artifacts can be found at `C:\Users\sasaares\AppData\Local\Temp\cargo-install1PHDae`.   
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

This might be as good as any place to start defining the development environment setup process.