Issue:
Bug: [$100] Develop Email Template Design



### Please make sure to read this through the below Guidelines before attempting the problem statements

[Contribution Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
[Bounty Program Guidelines](https://github.com/juspay/hyperswitch/wiki/Guidelines-for-Bounty-Program)
[Terms of Contest](https://github.com/juspay/hyperswitch/blob/main/docs/TERMS_OF_CONTEST.md)

## Context

As part of automating the welcome email process for merchants signing up to our dashboard, we need to create a visually appealing, fully responsive email template based on the design provided in the Figma file. The template will serve as the welcome email for merchants, replacing the current manual process, and must align with our brand guidelines.

  #### **Requirements:**

  - Follow the design provided in the Figma file: [Figma Link](https://www.figma.com/design/lhmTvW2vuc2p5B4ZvsEOTw/Email-Tempalte-Design?node-id=0-1&t=OKWmXqVOsidKUk7y-1)
  - Utilize existing assets (images, logos, icons, etc.) found in the figma.
  - Ensure the template is fully responsive and compatible with major email clients (e.g., Gmail, Outlook, Apple Mail).
  - Include all the design elements such as header, body content, call-to-action button, and footer as outlined in the Figma file.
  - Write clean, maintainable, and well-documented code.

  #### **Acceptance Criteria:**

  - Email template developed according to the Figma design.
  - The template is responsive and displays correctly across major email clients.
  - The design aligns with the brand style guidelines.
  - Code is properly commented and documented.
  - A preview of the email template is provided.

  #### **Additional Notes:**

  If you have any questions regarding the design or assets, please drop a message in our Community Channels


Pull request description:
## 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 fixes the command used to generate release notes in the release new version workflow.

## 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).
-->
The current command handles things much better and avoids trimming of changelog entries unnecessarily.

## 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)?
-->
Locally. Trust me, it works.

## 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


Testing:

Locally. Trust me, it works.

Patch: