fix: cluster not reachable handling

[prakash100198]

Description

When we click on the Resource Browser tab, there is no information about the cluster i.e if the cluster is active or has died on the upfront so that user can see it on the home page. So the error in connecting with the cluster is not being sent int hte api response for the frontend to handle.

How Has This Been Tested?

• I tested my code locally, while checking the api response when we click on the Resource Browser tab

Checklist:

• The title of the PR states what changed and the related issues number (used for the release note).
• Does this PR requires documentation updates?
• I've updated documentation as required by this PR.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have tested it for all user roles.
• I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication