Gracefully handle gpg signature info in git log output

[ghengeveld]

If the user has showSignature = true configured for their Git environment, any invocation of git log will print additional information about the gpg signature, which causes an error. With this update, such gpg signature lines are ignored.

📦 Published PR as canary version: 7.2.4--canary.833.2fed8db.0

✨ Test out this PR locally via:

npm install chromatic@7.2.4--canary.833.2fed8db.0
# or 
yarn add chromatic@7.2.4--canary.833.2fed8db.0

[linear]

AP-3591 CLI breaks when `showSignature` is configured for Git

How is the user affected? And what is the expected behavior?

If the user has showSignature = true configured for their Git environment, any invocation of git log will print additional information about the gpg signature. This then gets passed along to the index as if it's a commit hash, but that's not valid and causes a GraphQL error.

How many and/or what class of users does this impact?

Users with showSignature = true configured in their local or global Git config.

Is there a workaround?

Disable showSignature.

What are the steps for reproducing the issue?

See #806

Other information

We could add --no-show-signature to the git log commands we run, but that wouldn't work with older Git versions. Instead it would be better to parse the output of the git log command to trim any suffix information such as the gpg signature.

[thafryer]

LGTM!