CI: Remove grep from asv call (using strict parameter instead)
Looks like asv didn't fail the CI, because if requires a `--strict` parameter to do so. Adding it here. And will change this behavior in asv: https://github.com/airspeed-velocity/asv/issues/1199

Adding a failing benchmark to make sure this works as expected. Will remove if CI is red because of it.
Looks like this is working as expected, CI will now fail if benchmarks break, without the grep hack: https://github.com/pandas-dev/pandas/runs/5817260505?check_suite_focus=true#step:6:12445 Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

```
git checkout 1.4.x
git pull
```

2. Cherry pick the first parent branch of the this PR on top of the older branch:
```
git cherry-pick -x -m1 c8cbe1936d21503e82c6a9efeb133acaff4f845a
```

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

```
git commit -am 'Backport PR #46633: CI: Remove grep from asv call (using strict parameter instead)'
```

4. Push to a named branch:

```
git push YOURFORK 1.4.x:auto-backport-of-pr-46633-on-1.4.x
```

5. Create a PR against branch 1.4.x, I would have named this PR:

> "Backport PR #46633 on branch 1.4.x (CI: Remove grep from asv call (using strict parameter instead))"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the `Still Needs Manual Backport` label once the PR gets merged.

If these instructions are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
                