ci: auto bump version for meshery, extensions and cloud

[jerensl]

Notes for Reviewers

This PR fixes #

Signed commits

• Yes, I signed my commits.

[leecalcote]

This is helpful. And aids in DevEx. Thank you for working on this @jerensl.

Loopholes still exist even with this automation in place. Our foremost need in this area (release safety) is to enhance the "package.json syncer" (a Javascript file from @aabidsofi19 package-synced.js) that exists in meshery-extensions to ensure that if external dependencies fail to reconcile (be the same between Meshery UI and Meshery Extensions that the "Build and Publish" workflow is failed and email is sent (akin to the logic performed for go.mod syncer).

[leecalcote]

This is helpful. And aids in DevEx. Thank you for working on this @jerensl.

Loopholes still exist even with this automation in place. Our foremost need in this area (release safety) is to enhance the "package.json syncer" (a Javascript file from @aabidsofi19 package-synced.js) that exists in meshery-extensions to ensure that if external dependencies fail to reconcile (be the same between Meshery UI and Meshery Extensions that the "Build and Publish" workflow is failed and email is sent (akin to the logic performed for go.mod syncer).

@aabidsofi19 @jerensl should we proceed here in acknowledgment that this doesn't completely circumvent a potential issue, but that it is a boon to DevEx?