Summary

• fda814b: Make the autoharness filter flags work on the standard library by moving them to kani_compiler_flags, which ensures they're passed to all Kani compiler invocations.
• c0430ec: Print the crate name in our output tables.
• 093fc6b: Breaking Change to rename --include-function and --exclude-function to mention patterns instead, which makes it clearer that they talk about substrings of the total paths (e.g., modules). Also implement the suggestion from Autoharness Misc. Improvements #3922 (comment) so that the flags are no longer mutually exclusive.
• 9e35fca: Let the above flags filter on crate names as well.
• 66444e4: Warn if an exclude flag makes an include flag moot.

Detail

Some more context on why f933799c54b09210cb267963ff1dc431c7a9385a allows for both flags to be passed now: I realized as part of #3984 how when we call cargo rustc for a cargo kani invocation, we don't pass --reachability to dependencies to avoid running harnesses in them. The problem is that we can't do the same for our cargo command to build the standard library, since that uses cargo build, which does not have the same ability to pass flags only to the final compiler invocation and not the dependencies. So we end up passing --reachability=AllFns to the dependencies of the standard library as well and generate automatic harnesses for them. If we can pass both filter flags, we can run commands like kani autoharness --std --include-pattern core --exclude-pattern miniz_oxide, which will include functions from the core crate while excluding functions in the miniz_oxide that just happen to have the word "core" in them.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.