Add GSC to crater

[rsheeter]

Rev is just latest from https://github.com/googlefonts/googlesans-code/commits/main/

[cmyr]

So we have a bit of a problem here, which is that we really expect config files to be in either a sources or Sources directory, but this repo uses a source directory.

We had a similar issue with GS, where everything was in a source directory, and there was no config.yaml; we solved that issue by adding sources/config.yaml and then pointing from there to the actual sources located in the source directory.

However this repo has a config.yaml, it's just in the wrong place.

Some possible solutions:

• add support in google-fonts-sources for sources living in a source directory. This wouldn't be too annoying, but it feels a little bad to do this work for a single case, when we really expect fonts to use source or sources.
• fix this in the GSC repo (rename source to sources). This seems easy, but I'm not sure what breakage could result.
• fix this in the GSC repo by adding a sources directory containing a symlink'd config.yaml. This one scares me a bit, because... symlinks. Does anyone use windows?

[rsheeter]

Can we add it and let it fail until one of the solutions has occurred? - I'll follow up with GSC about renaming source

[cmyr]

we can, although if the fix requires an update in GSC we'll have to PR this again with a rev that includes the fix.

[chrissimpkins]

We can make the directory path update. I reached out to @belluzj today to see what we need to do in the CI build workflow to accommodate this path change.

@MariannaPaszkowska for future reference, we should begin to use sources regularly for our source directory paths to support the crater requirements here.

[cmyr]

And to clarify, we expect sources because that is what is used in the google-fonts-project-template: https://github.com/googlefonts/googlefonts-project-template/blob/main/sources/config.yaml