Add test cases for improving test coverage of release notes tools generator

[chandankumar4]

What would you like to be added (User Story)?

Add Unit test case for improving test coverage for release notes tools

Detailed Description

Reference: #10931 (comment)

Anything else you would like to add?

No response

Label(s) to be applied

/area testing
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.

[sbueringer]

/triage accepted

[sbueringer]

/help

[k8s-ci-robot]

@sbueringer:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[irapandey]

Hey @sbueringer ,

I am interested in working on the issue. I am fairly new to contributing to this repository.

Based on my understanding of the issue, the tool responsible for generating release notes is adding Release notes PR in the notes, which is not required.

The test case should be making sure that this doesn't happen in the future - PRs with ":rocket:" 🚀 shouldn't be a part of release notes.

Let me know if I am missing somethings.

Thanks 😄