chore: Automate release process with melos-action

[grdsdev]

What kind of change does this PR introduce?

chore

What is the current behavior?

Releasing and publishing is all done manual by running melos commands.

What is the new behavior?

Setup github actions for automating the release process.

Additional context

Add any other context or screenshots.

[coveralls]

Pull Request Test Coverage Report for Build 18099815998

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.03%) to 80.511%

---

Files with Coverage Reduction	New Missed Lines	%
packages/postgrest/lib/src/postgrest_query_builder.dart	1	94.92%

Totals
Change from base Build 17918038339:	0.03%
Covered Lines:	3119
Relevant Lines:	3874

---

💛 - Coveralls

[Vinzent03]

What is the plan with this block? Do we want GitHub releases as well or only tags?

[grdsdev]

Uncommented.

I didn't test this whole workflow yet, lets get it merged and try to create a release using it