UX Framework: CI health badges component with simple server API

[franks883]

PR Description:

Adds a small Now Experience style component that renders CI health as Good, Warning, or Critical. Includes a Script Include (CiHealthApi) returning a minimal JSON shape and a client component snippet that calls it and renders a badge.

Includes README, client snippet, and server Script Include.

Pull Request Checklist

Overview

• Put an x inside of the square brackets to check each item.
• I have read and understood the CONTRIBUTING.md guidelines
• My pull request has a descriptive title that accurately reflects the changes and the description has been filled in above.
• I've included only files relevant to the changes described in the PR title and description
• I've created a new branch in my forked repository for this contribution

Code Quality

• My code is relevant to ServiceNow developers
• My code snippets expand meaningfully on official ServiceNow documentation (if applicable)
• I've disclosed use of ES2021 features (if applicable)
• I've tested my code snippets in a ServiceNow environment (where possible)

Repository Structure Compliance

• I've placed my code snippet(s) in one of the required top-level categories:
  • Core ServiceNow APIs/
  • Server-Side Components/
  • Client-Side Components/
  • Modern Development/
  • Integration/
  • Specialized Areas/
• I've used appropriate sub-categories within the top-level categories
• Each code snippet has its own folder with a descriptive name

Documentation

• I've included a README.md file for each code snippet
• The README.md includes:
  • Description of the code snippet functionality
  • Usage instructions or examples
  • Any prerequisites or dependencies
  • (Optional) Screenshots or diagrams if helpful

Restrictions

• My PR does not include XML exports of ServiceNow records
• My PR does not contain sensitive information (passwords, API keys, tokens)
• My PR does not include changes that fall outside the described scope

[ravichandra1998g]

Thank you for your contribution!
CMDB health is a crucial component in an instance.

We have OOB CMDB health dashboard and CMDB workspace to get various insights, visualization and also to know CIs health based on completeness, correctness and compliance.

I do not see any reason to query a custom table for a huge table like CMDB CI to get a CI health as we already have that setup OOB.

Closing this PR now. Please provide another contribution with dynamic use cases/contexts.