Bug: Cargo Deny Fails when --manifest-path Cargo.toml is Provided

[George-lewis]

Describe the bug

Cargo deny exits with an error, apparently originating from cargo metadata, when a manifest path is provided which does not begin with a folder

To reproduce

In a Rust project, in the folder containing Cargo.toml,

Running cargo deny --manifest-path Cargo.toml check all fails with error:

failed to start `cargo metadata`: No such file or directory (os error 2): No such file or directory (os error 2)

However, running cargo deny --manifest-path ./Cargo.toml check all works without issue

Furthermore, cargo metadata --manifest-path Cargo.toml works as well

cargo-deny version

0.14.17

What OS were you running cargo-deny on?

Linux

Additional context

No response