Bump git-utils & Migrate to yarn

[confused-Techie]

This PR requires #2

Due to #2 and the usage of yarn being required for successfully building the repository, I've also migrated to a yarn.lock file and removed package-lock.json to ensure it's obvious which one we are using.

---

The main meat of this PR and it's actual purpose though is to upgrade git-utils. The reason for this is two-fold:

• Obviously upgrading dependencies is always a good thing when it's non-breaking.
• More importantly, and the reason for doing this is looking at our unpacked ASAR archive of an installed Pulsar shows that we have two copies of git-utils.

One copy is required by Pulsar itself at [email protected] and the other from this repository scandal at [email protected]. I'm hoping the differences in these versions have zero affect on scandal, considering how little of a version difference it is.

But the reason this is important is in an unpacked ASAR archive:

• [email protected]: 85.8MB
• [email protected]: 85.1MB

Meaning if we sync the versions of this dependency between Pulsar and scandal we will be able to remove 85.1MB off of our install size, which while not huge on it's own, this is by far our biggest single dependency. So would be the best starting point at trying to reduce our install size and duplicated dependencies.

[DeeDeeG]

Interesting. I found that updating git-utils is required, as the outdated [email protected] doesn't compile against Node 16. So, this PR's changes and #2 should ideally be done in one PR, I guess.

Or else do one PR that flips CI on (possibly failing/red CI if done first) and another PR that gets us newer git-utils.

But I think doing both is necessary to have working CI for this repo, perhaps slightly ironically.

[confused-Techie]

Replaced by #5