@celo/abis and @celo/contracts should not be available to publish by default

[shazarre]

Description

This PR sets removes version and marks as private @celo/abis and @celo/contracts packages to avoid releasing valid version by mistake.

Other changes

None.

Tested

Ran RELEASE_VERSION=10.0.0-local yarn prepare_contracts_and_abis_publishing to see if it still replaces versions in package.json and it does (as well as marks the packages as public).

Ran yarn prepare_contracts_and_abis_publishing to see if it doesn't replace versions in package.json and it doesn't. It also keeps the packages private.

Ran the workflow manually and noticed that package has been released with provided tag. For automated runs after commits it didn't release anything as expected.

Backwards compatibility

It's backwards compatible.

Documentation

None.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9090105

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[aaronmgdr]

defensive coding

[aaronmgdr]

need something that doesnt error out but also wont accidently publish

[aaronmgdr]

i feel like i remember having an issue setting private: false, before where it would complain that it should just be removed. maybe that was just a lint and not an real isssue.