Add clang-tidy details to current check

[jwrober]

In order for us to have a clang-tidy pre-check like we do for clang-format we need to fully know what the CI is going to see. Adding code to the existing CI to run against the whole tree. It will always fail, but for me that is ok. We use it for diagnostics.

Part of #2464
part of #3000

[lmoureaux]

A failure in utility will prevent the workflow from continuing. Since we have continue-on-error, what about a structure like this:

1. utility - if this fails, the job fails
2. common - if this fails, the job fails
3. ai client server tools - still allowed to fail for now

Then we move folders from 3 to 1 over time.

[jwrober]

A failure in utility will prevent the workflow from continuing. Since we have continue-on-error, what about a structure like this:

1. utility - if this fails, the job fails
2. common - if this fails, the job fails
3. ai client server tools - still allowed to fail for now

Then we move folders from 3 to 1 over time.

This is effectively what I was thinking too. I have a branch in my local I started testing with yesterday when I realized the repo isn't quite ready. The test for utility and common I think can be combined. I kept utility separate because of the spec*.h files that don't pass any kind of IWYU check due to their nature.

[jwrober]

I'll need to bring in #3001 and #3002 in here in a rebase for this to work as expected.

[lmoureaux]

Both merged