Smart contracts 0.8.0 release

[quiet-node]

Problem

New smart contracts and features need to be captured in a new release

Solution

• [x] Create a release/0.8 branch from the latest commit in main.
• [x] Create a new branch named bump-0.8.0-rc1. Submit a 0.8.0-rc1 bump PR from the bump-0.8.0-rc1 branch to the release/0.8 branch. This PR should only update the version statement in package.json and package-lock.json to 0.8.0-rc1. (Example: https://github.com/hashgraph/hedera-smart-contracts/pull/631)
• [x] Create a new branch named bump-0.9.0-snapshot. Submit a 0.9.0-SNAPSHOT bump PR from the bump-0.9.0-snapshot branch to the main branch. This PR should only update the version statement in package.json and package-lock.json to 0.9.0-SNAPSHOT. (Example: https://github.com/hashgraph/hedera-smart-contracts/pull/632)
• [x] Establish a new release with the title v0.8.0-rc1, tageting release/0.8 branch, and set it as pre-release. Simultaneously create a corresponding tag with the same title for the release. Publish the release. (Example: v0.7.0-rc1 release)
• [x] Establish a new release with the title v0.8.0, targeting release/0.8 branch, and set it as latest release.Simultaneously create a corresponding tag with the same title and compose the release note. Publish the release. (Example: v0.7.0 release)

Alternatives

No response