Contract release versions

[han-so1omon]

What needs to be done

Establish release versions for smart contracts

Why it needs to be done

The release versions of CPS contracts are currently untracked. This means that it is uncertain which version of the contracts on testnet or mainnet corresponds to which versions of the contracts in the upstream code repository

Acceptance Criteria

• Create a semantic versioning system for the CPS contracts following the widely accepted standard
• Create a Github Action pipeline to be triggered on contract release using standard practices for monorepos
• Ensure that the pipeline only succeeds if all unit and integration/regression tests succeed