Fixes: #128

Avoid some problems with relative paths by attempting to expand. Still
fall back to the originally provide path if canonicalization fails.

Fixes: #227

Currently this crate has no clear MSRV. Pick a common ecosystem point of
1.65 (let-else!) and start testing that in CI.

We could easily bump this further if needed, but there isn't much active
development and it is unlikely to be a point of contributor friction. We
can't easily be much below this because of `cc`.

This should fix the `Error: could not load cache` BUG.

If there are already generated build files in the project directory,
then if you execute the command `cmake path/project` in
`$OUT_DIR/build`, cmake will not generate new build files in the
`$OUT_DIR/build` directory.

So `-B .` is needed.
https://cmake.org/cmake/help/latest/manual/cmake.1.html#cmdoption-cmake-B

Example:

```sh
cd /path/to/project
cmake .         
# output `Build files have been written to: /path/to/project`
cd /path/to/build && cmake /path/to/project
# we expect the build files will be generated at current dir (/path/to/build)
# but unfortunately get `Build files have been written to: /path/to/project`
cd /path/to/build && cmake /path/to/project -B .  
# output `Build files have been written to: /path/to/build`, that is right!
```

Infomation:
```
cmake --version
cmake version 3.27.7

CMake suite maintained and supported by Kitware (kitware.com/cmake).
```

I have tested this and it appears to work well.

Fixes #253

When a path is canonicalized on Windows, a `\\?\` prefix is used.
However, it appears that cmake can have problems with that. This simply
attempts to remove the prefix as we do still want to use absolute path
here due to #200.

Fixes #258

## 🤖 New release

* `cmake`: 0.1.54 -> 0.1.55 (✓ API compatible changes)

<details><summary><i><b>Changelog</b></i></summary><p>

<blockquote>

##
[0.1.55](v0.1.54...v0.1.55)
- 2025-12-11

### Other

- Remove the `\\?\` prefix from paths
([#259](#259))
- Add Visual Studio 2026 support
([#255](#255))
- Make sure that cmake generate build files in current dir
([#194](#194))
- Set the MSRV to 1.65 and test this in CI
- Canonicalize the build directory
- Use `eprintln` instead to print the command running next
([#191](#191))
</blockquote>


</p></details>

---
This PR was generated with
[release-plz](https://github.com/release-plz/release-plz/).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>