feat(cd): enable deployments via GitHub releases

[Nitish145]

Describe the changes you have made in this PR -

• Uses GitHub releases & associated tags to ship the app to play store.
• gh-actions accepts 'vx.y.z-beta' for beta builds and 'vx.y.z' for prod builds.

Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

[coveralls]

Pull Request Test Coverage Report for Build 1135272599

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 15 unchanged lines in 1 file lost coverage.
• Overall coverage remained the same at 74.053%

---

Files with Coverage Reduction	New Missed Lines	%
lib/ui/views/cv_landing_view.dart	15	59.8%

Totals
Change from base Build 1126029342:	0.0%
Covered Lines:	3910
Relevant Lines:	5280

---

💛 - Coveralls

[manjotsidhu]

We can delete deploy branch after merging this since it will not be required. Also, a corner case would be where I can make release based off branch another than master. I feel we should only allow from master branch.

[tachyons]

https://github.com/xotahal/fastlane-plugin-semantic_release

[tachyons]

https://bumped.github.io/

[tachyons]

https://www.conventionalcommits.org/en/about/ There are some tools listed here, we should explore them as well to improve the workflow by making use of conventional commits structure we decided to follow

[Nitish145]

https://github.com/xotahal/fastlane-plugin-semantic_release

This looks great! @manjotsidhu would you want to take this ahead? Maybe in this PR or another one.

[manjotsidhu]

https://github.com/xotahal/fastlane-plugin-semantic_release

This looks great! @manjotsidhu would you want to take this ahead? Maybe in this PR or another one.

Sure, I think we can handle that in a new PR.