Explicitly pass --config-file

[mattlangford]

It seems like relying on the default .clang-tidy config file means that --verify-config doesn't actually fail the call. This looks like it works when I add random characters to the .clang-tidy file in this repo

$ bazel build //... --config clang-tidy
...
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
.clang-tidy:9:1: error: unknown key 'asdf'
asdf
^~~~
Error: invalid configuration specified.
Invalid argument
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 0.192s, Critical Path: 0.09s
INFO: 7 processes: 4 action cache hit, 7 internal.
ERROR: Build did NOT complete successfully

[dotnwat]

Confirmed locally that this PR addresses the issue. Thanks @mattlangford

[dotnwat]

I think this probably fixes #69 as well. The simplest explanation is that I had introduced errors into the clang tidy configuration file and was experiencing silent fallbacks to the default config.

[erenon]

Thanks!