Issue:
ci: add workflow to create tags on schedule

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [x] CI/CD

## Description
<!-- Describe your changes in detail -->
This PR introduces a new workflow to create tags on schedule, with the aid of `cocogitto`. In addition, this adds a `cocogitto` template for updating the changelog file. The changelog file has also been updated with recent changes.

I'll take up generating the release notes and GitHub release in a separate PR.

## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.

If you don't have an issue, we'd recommend starting with one first so the PR
can focus on the implementation (unless its an obvious bug or documentation fix
that will have little conversation).
-->
We aim to have daily releases.

## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant screenshots)?
-->
https://github.com/juspay/hyperswitch/actions/runs/5474468598

## Checklist
<!-- Put an `x` in the boxes that apply -->

- [ ] I formatted the code `cargo +nightly fmt --all`
- [ ] I addressed lints thrown by `cargo clippy`
- [x] I reviewed submitted code
- [ ] I added unit tests for my changes where possible
- [ ] I added a [CHANGELOG](/CHANGELOG.md) entry if applicable


Resolution:
<think>
PR Context:
- Title: ci(release-new-version): create GitHub release with release notes
- Merged: 2023-07-10T13:44:07Z
- Files changed: 8 files
- Commits: 8 commits

Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [x] CI/CD

## Description
<!-- Describe your changes in detail -->
This PR adds support for the "release a new version" workflow to also create a GitHub release in addition to a tag.

## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please
</think>

To implement this, you'll need to modify:


(No detailed commit information available)