Make --include and --exclude use prefix matching.

[nnethercote]

In #1138 I changed --include/--exclude to do exact matching of
benchmark names. This was a good idea at the time, but since then we
have renamed many benchmarks. There is now no benchmark with a name that
is a prefix of another benchmark's name. Also, we now have version
numbers in many benchmark names, which are a pain to remember and type.

This commit lets you specify a benchmark name by prefix. E.g.
--include=stm will match stm32f4-0.14.0.

[Kobzol]

I was quite fond of the new exact matching behaviour, but it's true that after TBBU (the big benchmark upgrade) it's quite annoying and prefixes are the way to go 👍

The PR and commit name seems to be wrong (it describes the previous change).

[rylev]

This makes a lot of sense. I am worried we'll end up hitting the old gotcha if we introduce something like serde_json as a benchmark...

[Kobzol]

The code could assert that the benchmarks don't share prefixes, this would be then caught in tests on CI if such benchmark would be introduced. But it would be a bit fragile (a prefix can also be a single char..) and it would not allow us to add serde-json, which is not good.

Maybe we could just print a warning/info log if a prefix matches more benchmarks? Although if the documentation/help explicitly says that it uses prefixes, that's kind of the expected behaviour.

[nnethercote]

This makes a lot of sense. I am worried we'll end up hitting the old gotcha if we introduce something like serde_json as a benchmark...

Presumably that would be serde_json-1.0.79 or similar, so you could use serdeif you want to match multiple or serde-/serde_ if you just want to match one.

[rylev]

It's probably not that bad if someone accidentally matches more than benchmark so I'm fine with merging this. We can just keep an eye out if this causes issues in the future.

[nnethercote]

I was going to fix the commit message, but it's already been merged :)

[rylev]

Whoops! Sorry! 😀