Due to https://issues.redhat.com/browse/ACM-2589, the Discovery automation is failing trying to detatch a cluster.

I also hit this defect which made the fix more challenging, but with help from the Console team, I was able to come up with a solution: https://issues.redhat.com/browse/ACM-20377

Slack discussion: https://redhat-internal.slack.com/archives/C0804HR2D41/p1746448224546389

Old Function:
function selectDetachOption(clusterName) {
cy.log(`Cluster to be detached: *${clusterName}*`)
cy.contains(clusterName).parents("tr").within( () => {
cy.get(".pf-m-fit-content").click()
cy.get("#detach-cluster")
.within( $el =>

{ cy.get('a') .should('have.attr', 'aria-disabled', 'false') }

)
.pipe(click)
.should($el =>

{ expect($el).to.not.be.visible })
})
}

New Function:
function selectDetachOption(clusterName) {
cy.log(`Cluster to be detached: *${clusterName}*`)
cy.contains(clusterName).parents("tr").within( () => {
cy.get(".pf-m-fit-content").click()
cy.get("#detach-cluster")
.should('have.attr', 'aria-disabled', 'true')
.pipe(click)
.should($el => { expect($el).to.not.be.visible }

)
})
}