CI: Validate Cargo.toml's `repository` vs the value from the cloned repo

It's possible for the `repository` field in Cargo.toml and the actual location of the cloned repo to disagree with each other. If this happens, it can lead to inconsistencies in the CI process later; for example, trying to run `cargo dist plan` when publishing to axo releases will result in an attempt to ask the API about the wrong repo. We should try to catch this.

Start with the repository field in Cargo.toml and the cargo dist plan entry point, then inspect how the cloned repository location is available during CI. The work is done when CI detects and reports a mismatch before the later axo releases publishing flow can query the wrong repository.

Written by the indexing model from the issue text.