verify-rust-std generates autoharnesses of kani which brings more function calls especially with closures in names

[zjp-CN]

Example of https://github.com/os-checker/distributed-verification/blob/e01dc705a25fbaecb5367e640ab758250e851367/tests/snapshots/verify-rust-std/names_not_in_functions.txt

    "char::convert::from_u32_unchecked::{closure#0}::{closure#1}::{closure#1}::precondition_check",
    "char::convert::from_u32_unchecked::{closure#2}::{closure#1}::precondition_check",
    "char::convert::from_u32_unchecked::{closure#3}::{closure#0}::precondition_check",

These calls probably come from -Z autoharness --include-pattern

• https://github.com/model-checking/verify-rust-std/blob/e021729236fa4a3645b570b09cebc099c4c23eee/.github/workflows/kani.yml#L109
• https://model-checking.github.io/kani/reference/experimental/autoharness.html?highlight=--include-pattern#options

The solution is to support passing extra kani arguments to verify_rust_std CLI.

[zjp-CN]

• cc Tracking Issue: Automatic Harnesses model-checking/kani#3832 (comment)
• cc Move autoharness_analyzer to scripts/ model-checking/verify-rust-std#350 (comment)

I don't think these differences are big troubles, because they're filtered out when run as autoharnesses. While in standard harnesses, they don't even exist.