chore(release): prepare for release

[vbuberen]

Description

Long awaited release of packages.

To workaround the problem we had with publishing that we had when share_plus dry run failed due to not being able to find the share_plus_platform_interface I have changed version of platform interface to be not 3.2.1 which we are going to publish, but 3.2.0. With this change we are able to run melos publish successfully and I don't expect breaking changes caused by this changes.

As soon as I publish this release I will create a new release for share_plus plugin only which should publish successfully as platform interface 3.2.1 will be already available on pub.dev.

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I titled the PR using Conventional Commits.
• I did not modify the CHANGELOG.md nor the pubspec.yaml files.
• All existing and new tests are passing.
• The analyzer (flutter analyze) does not report any problems on my PR.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
• No, this is not a breaking change.

[nohli]

Yay

[vbuberen]

Due to #1628 we also need to update our workflows file to run melos bootstrap, which should take care of dependency overrides.

[vbuberen]

All failing tests seems to be about version resolution, which I plan to address after this release, so merging the PR.