ci: add reusable workflow to create nightly tags in CalVer format

[SanchithHegde]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

This PR adds a new reusable workflow to create tags in the calendar versioning (CalVer) format YYYY.0M.0D.MICRO (month and date are zero-padded, and the MICRO version number starts from zero) instead of the existing release-new-version workflow to create SemVer tags. The workflow uses a GitHub app token and GitHub API calls to commit the changes and tag them in order to have verified commits and tags.

The reusable workflow can be used like so (provided the secrets have been set up):

jobs:
  create-nightly-tag:
    name: Create a nightly tag
    uses: juspay/hyperswitch/.github/workflows/release-nightly-version-reusable.yml@main # Or ...@<commit_sha>
    secrets:
      app_id: ${{ secrets.HYPERSWITCH_BOT_APP_ID }}
      app_private_key: ${{ secrets.HYPERSWITCH_BOT_APP_PRIVATE_KEY }}

Refer to the docs for more information.

Prerequisites for using the reusable workflow

1. The first CalVer tag must be tagged manually (by some user), the workflow does not handle that case.
2. The workflow needs a git-cliff configuration file located at .github/git-cliff-changelog.toml.

Motivation and Context

We will be using CalVer tags for daily tags, which will be used internally for testing, and SemVer tags for stable releases which are meant to be used by end users.

How did you test it?

I temporarily updated the workflow file to run on this branch, the commits in this PR include the commits pushed by the bot. Note that the commits created by the bot are also signed.

One of the action runs: https://github.com/juspay/hyperswitch/actions/runs/7401505144

As a proof of the tag that was created by the bot, I'm including a screenshot of the tag that was pushed (which was since deleted). Note that the tag created is also signed.

The 2024.01.03-test-tag had to be created manually by me because the workflow does not handle that case.

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible
• I added a CHANGELOG entry if applicable