allow other directors that tools/ for the wrapper

Hi, can we have BAZELISK_WRAPPER_DIR variable where we can e.g. bin as the directory of the wrapper? Or, alternatively, a BAZELISK_WRAPPER= that points directly to the wrapper. We'd then loose then the various extensions it supports ... but if someone configures the wrapper in the .bazeliskrc file, then this might not be a problem.

The reason is that the current tools/ constant forces a policy into all usages. I.e. any repository that wants to use this bazel feature needs a top-level "tools/" directory which might not be prudent for the project. Or for the projects leaders opinion ...

Start by locating the code that assumes a top-level tools/ directory and the handling of .bazeliskrc. Trace how the wrapper is selected, then define the configuration behavior for an alternate directory or direct wrapper path. Done means repositories can configure either option without being forced to add tools/, with tests covering the selected behavior.

Written by the indexing model from the issue text.