It can be common to call kondo on a path that does not exist, which yields quite badly-looking panic message:

$ kondo does-not-exist
thread 'main' panicked at 'Unable to canonicalize!: Os { code: 2, kind: NotFound, message: "No such file or directory" }', kondo-lib/src/lib.rs:320:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This PR still does not quite solve that, since the error message now looks like:

$ kondo does-not-exist
Error: Os { code: 2, kind: NotFound, message: "No such file or directory" }

kondo's error treatment is generally still quite lacking but I feel like this PR is a step in the right direction, specially if it could adopt the usage of the fs-err crate in the future