OSD-28506: feat(Add Handover Announcements to Cluster Context Command)

[devppratik]

We are looking to migrate from the Handover Doc to a JIRA based Handover Board. This would allow to use JIRA queries to directly display related handover announcements at the time of login for the cluster based on ID, Customer Name, Version and Product.

This PR adds the functionality to query JIRA and print the related announcements for the cluster.

Related Issue OSD-28505

[openshift-ci-robot]

@devppratik: This pull request references OSD-28506 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

We are looking to migrate from the Handover Doc to a JIRA based Handover Board. This would allow to use JIRA queries to directly display related handover announcements at the time of login for the cluster based on ID, Customer Name, Version and Product.

This PR adds the functionality to query JIRA and print the related announcements for the cluster.

Related Issue OSD-28505

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 openshift-eng/jira-lifecycle-plugin repository.

[chamalabey]

@devppratik I have started testing your changes and noticed that cluster context does not show the announcement for staging cluster 2ja1c3di93h0jk8mm0h12hg7jg83nap2 with the announcement https://issues.redhat.com/browse/SREPHOA-9
Please have a look and let me know if I am missing something .

[chamalabey]

Thank you @devppratik for the MR.

When testing, have noticed that cluster context command is returning same announcement twice when the announcment is for the cluster id and may be the version. We might need to remove duplicates in the list before we print the results of the JIRA query.
e.g. in staging

✘-127 ~/Documents/workspace/sre/github.com/openshift/osdctl [add-handover-announcements-for-osdctl-cluster-context L|✔] 
16:30 $ ./dist/osdctl_linux_amd64_v1/osdctl cluster context --cluster-id 2ja1c3di93h0jk8mm0h12hg7jg83nap2WARN: The current version (v0.44.2-next) is different than the latest released version (v0.44.2). It is recommended that you update to the latest released version to ensure that no known bugs or issues are hit.
Continue? (y/N): y
Encountered Errors during data collection. Displayed data may be incomplete: 
	skipping PagerDuty context collection: Could not build PagerDuty Client - No configured tokens
============================================
incident -- 2ja1c3di93h0jk8mm0h12hg7jg83nap2
============================================
ID:				2ja1c3di93h0jk8mm0h12hg7jg83nap2
External ID:			544bda53-5c34-4653-963e-b671f34b20f8
Name:				incident
Domain Prefix:			incident
Display Name:			incident
State:				ready 
API URL:			https://api.incident.jtir.s3.devshift.org:443
API Listening:			external
Console URL:			https://console-openshift-console.apps.rosa.incident.jtir.s3.devshift.org
Cluster History URL:		https://cloud.redhat.com/openshift/details/s/2yFwOzJakdQ5wK1oKi449vNVxPA#clusterHistory
Control Plane:
				Replicas: 0
Infra:
				Replicas: 0
Compute:
				Replicas: 3
Product:			rosa
Subscription type:		marketplace-aws
Provider:			aws
Version:			4.16.34
Region:				us-east-2
Multi-az:			true
CNI Type:			OVNKubernetes
PrivateLink:			false
STS:				true
Subnet IDs:			[...]
CCS:				true
HCP:				true
Existing VPC:			true
Channel Group:			stable
Cluster Admin:			true
Organization:			Red Hat-Service Delivery-CSSRE
Creator:			xxx
Email:				xxx
AccountNumber:          	xxxx
Created:			2025-06-09T04:33:21Z
Expiration:			2025-06-12T21:53:15Z
.
.

>> Related Handover Announcements
[SREPHOA-9]: Test
- Link: https://issues.redhat.com/browse/SREPHOA-9

[SREPHOA-9]: Test
- Link: https://issues.redhat.com/browse/SREPHOA-9

[SREPHOA-8]: ROSA HCP 4.14 clusters are being force upgraded
- Link: https://issues.redhat.com/browse/SREPHOA-8

[SREPHOA-7]: Regarding HCP Clusters
- Link: https://issues.redhat.com/browse/SREPHOA-7

[SREPHOA-5]: Regarding OHSS tickets
- Link: https://issues.redhat.com/browse/SREPHOA-5

[SREPHOA-4]: Regarding PagerDuty Alerts
- Link: https://issues.redhat.com/browse/SREPHOA-4

[SREPHOA-3]: For issues related to ROSA HCP please consult the following spreadsheet, you might find it’s already tracked
- Link: https://issues.redhat.com/browse/SREPHOA-3

[openshift-ci]

@devppratik: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

[devppratik]

@chamalabey It has been fixed. Please review again

[chamalabey]

@devppratik Have tested and new changes looks good.

[chamalabey]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chamalabey, devppratik

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [devppratik]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[joshbranham]

Can you come back and add some tests for these new changes?

[devppratik]

@joshbranham Sure I can add some test cases, but the jira.go file would need to be refactored to make it mockable and testable. Will take up in a separate PR