Chore: setup release please

[cherylli]

Description

Create Release please yml file. The changes probably won't take effect till after next time we merge into main. It has been tested on my fork repo. We will need to make sure we start using squashed, conventional commits.

Fork: https://github.com/cherylli/chingu-dashboard-be/pulls
Release please: https://github.com/googleapis/release-please
Conventional commits: https://www.conventionalcommits.org/en/v1.0.0/
Squashing commits:
https://stackoverflow.com/questions/5189560/how-do-i-squash-my-last-n-commits-together
https://github.com/chingu-x/chingu-dashboard-be/wiki/Getting-Started

We will still maintain the changelog in the period of transition, till we completely follow conventional commits

Updated Wiki: https://github.com/chingu-x/chingu-dashboard-be/wiki/Getting-Started

Issue link

BE-25-013

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature updates / changes
• Tests
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have updated the change log

[github-actions]

@timDeHof, @curtwl
One business day has passed since the review started. Give priority to reviews as much as possible.

[timDeHof]

The git action for my fork worked but created a new branch with the new changelog.md in it.

[cherylli]

The git action for my fork worked but created a new branch with the new changelog.md in it.

did you have a changelog.md in your fork? Mine just appended to the existing one.

[timDeHof]

The git action for my fork worked but created a new branch with the new changelog.md in it.

did you have a changelog.md in your fork? Mine just appended to the existing one.

no, I didn't have one. I created a working branch of the main branch of my fork.