Automatically create a release pull request by triggering a workflow

[toby-thanathip]

As of now, when it's time to create a release, we execute the following steps:

1. Create a release PR (manually) from develop, then merge it to master
2. Draft a new release (automatically, after merging to master) → draft-new-release.yml
   -> This was integrated in Add new workflow to generate Release note and version tag automatically #100
3. Create a bump version PR (automatically, after triggering the workflow manually) → bump_version.yml
   -> This was integrated in Automate New version bumping by Github action #301

As steps 2 & 3 are automated, so should we do the same for step 1 🚀

My idea is as follows:

1. Create a new workflow create_release.yml
2. Provide user input for the milestone (similar to what we did for bump_version.yml)
3. Use https://github.com/octokit/request-action to call GitHub API inside the workflow
4. Call List repository issues, with milestone parameter
5. Parse, filter, map, and organize the response with Kscript (similar to what we did for draft-new-release.yml)
6. Create a pull request with the output from our script (similar to what we did for bump_version.yml)

[lydiasama]

@Tuubz I have a question about how we trigger this workflow. My understanding is that we will trigger it manually from the github repository when the develop branch is ready to merge to main, not to set it to run this workflow automatically. So I voted Yes. Please correct me if I missed something. 🙏🏻

[toby-thanathip]

Yes, that's correct! Thank you, for pointing that out 🙏

It will be triggered manually from GitHub, with milestone as the input, to automatically create the PR 🚀

[chornerman]

Voted "Yes" 🚀

[luongvo]

I want to continue on this idea to have a new workflow to automate the release PR creation step. Do you want to continue on this or delegate to someone else @toby-thanathip?

[toby-thanathip]

Please take it 🙏 😂

[luongvo]

Ticket is created #525