Bug: [CI] Add ci workflow for validating hotfix pr



### Feature Description

Add support for creating a new workflow for validating the hotfix pr.
Workflow should be triggered when baseRef is prefixed with hotfix-


### Possible Implementation

Assumption -

Hotfix PR description contains one or more original PR's link
If description contains any issues link, it would be ignored
Validations include -
Among all the Original PR links added in Hotfix PR description, at least one has to satisfy the below conditions

Original PR author should be same as Hotfix PR author
Original PR title should be same as Hotfix PR title
Original PR's baseRef has to be main
Original PR should be merged to main

If no Original PR has been found in description or if above condition doesn't satisfy for even one original PR's, CI check will fail

### Have you spent some time checking if this feature request has been raised before?

- [X] I checked and didn't find a similar issue

### Have you read the Contributing Guidelines?

- [X] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)

### Are you willing to submit a PR?

Yes, I am willing to submit a PR!
## 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 a new workflow for validating the hotfix PR.
Workflow is triggered when baseRef of hotfix PR is prefixed with `hotfix-`

**Assumption** - 
  * Hotfix PR description contains one or more original PR's link
  * If description contains any issues link, it would be ignored

**Validations include** - 
  Among all the Original PR links added in Hotfix PR description, at least one has to satisfy the below conditions 
  * Original PR author should be same as Hotfix PR author
  * Original PR title should be same as Hotfix PR title
  * Original PR's baseRef has to be main
  * Original PR should be merged to main

If no Original PR has been found in description or if above condition doesn't satisfy for even one original PR's, CI check will fail

### Additional Changes

- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables

<!--
Provide links to the files with corresponding changes.

Following are the paths where you can find config files:
1. `config`
2. `crates/router/src/configs`
3. `loadtest/config`
-->


## 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 it is an obvious bug or documentation fix
that will have little conversation).
-->


## 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)?
-->
CI passing

![image](https://github.com/juspay/hyperswitch/assets/70657455/431347b5-99d6-4d77-af6c-36d9028cca34)

CI failing because Original PR is not merged

![image](https://github.com/juspay/hyperswitch/assets/70657455/1f6e1416-dfd2-4f7e-8bf9-a72468d8d8cb)


CI failing because Original PR title does not match with hotfix PR title

![image](https://github.com/juspay/hyperswitch/assets/70657455/dab1e61d-c6c4-4cf7-b90f-b0333ed48aa1)


## Checklist
<!-- Put an `x` in the boxes that apply -->

- [ ] 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](/CHANGELOG.md) entry if applicable
