Add a ThreadSanitizer build

msvc crtdbg -> win32 leakcheck

Add missing worktree_dir check and test case

The win32 leakchecking system is now named win32_leakcheck.  Update the
allocator to match.

Move leak check initialization into git_win32_leakcheck_global_init, and
call it on library initialization.

msvc crtdbg is a mouthfull that is not particularly indicative of what
it does.  Let's rename it to "win32 leakcheck".

Fix the `-DTHREADSAFE=OFF` build

ci: propagate environment variables

ci: supply a token for self-hosted runners

ci: supply a token for self-hosted runners

ci: GitHub Actions for arm64

ci: stop using deprecated set-env in GitHub Actions

(And move the ci scripts into the `ci` directory.)

Deprecate `is_valid_name` functions; replace with `name_is_valid` functions

Fixes #5280

worktree_dir isn't validated when it should be

This change avoids using the `(void)0` construct for some of the mutex
`#define`s, since that makes the "return type" of those "functions" to
be `void` instead of `int`.

Signed-off-by: Sven Strickroth <email@cs-ware.de>

Signed-off-by: Sven Strickroth <email@cs-ware.de>

Provide a function that can check remote name validity but can also
signal when an error occurs.  Use the name "name_is_valid", which is
more suggestive of checking a given name, rather than "is_valid_name",
which suggests that the function checks the validity of the current
remote's name.

Disambiguate invalid specifications in `git_refspec__parse` so that
callers can determine the difference between invalid specifications and
actual errors.  No call sites wil propagagte this new error message to
an end-user, so there is no user-facing API change.

Provide a function that can check reference name validity but can also
signal when an error occurs.  Use the name "name_is_valid", which is
more suggestive of checking a given name, rather than "is_valid_name",
which suggests that the function checks the validity of the current
reference's name.

Move `git_reference__is_valid_name` to `git_reference__name_is_valid`,
which returns errors and sets an out boolean parameter.

Include `${MBEDTLS_INCLUDE_DIR}` when compiling `crypt_mbedtls.c`

Without this, mbedTLS installs in non-default install locations
that are otherwise found by the `FindmbedTLS.cmake` module are not
found by the C preprocessor at compile time.