Invalid SHAs raise GRPC::InvalidArgument during the CI linting process
when the linter attempts to fetch local includes. We want to track the
invalid SHA values so we can understand how they are being included in
the query sent by the frontend on the pipeline editor page.