Remove private flag to prevent packaging issues in Yarn

[SamuelMS]

This PR drops private: true from the package.json file, since this appears to cause a known issue in Yarn 4 (a widely-used alternative to NPM) where new checksums are generated periodically, rather than being reproducible.

[Vilos92]

Hi @SamuelMS ,

We set private: true originally as there was no intention to publish the content of this repository as an npm package (see my response on the other issue). That said, I do not suspect it should be problematic to drop this flag. I will check with the team to confirm.

[Vilos92]

This has been resolved here: #16