Added QR Generator for Assets In UI Action Folder

[KUSHAL1912]

PR Description:

This pull request introduces a ServiceNow UI Action that generates and displays a QR Code for any selected Asset record.
When a user clicks the UI Action, the script retrieves asset data via a GlideAjax call and renders a QR Code in a modal window using the Qrickit API.

This contribution focuses exclusively on the UI Action (client-side) logic.
✨ Key Features
Adds a UI Action that displays a QR Code for the current Asset record.

Dynamically retrieves asset details using GlideAjax and a Script Include (GenerateAssetQR).

Uses the QrIckit API
to generate the QR image on the fly.

Presents the QR Code inside a GlideModal for quick access and scanning.

Includes a .png file showing example of the generated QR code.

⚙️ Technical Details

Client Script: qr_code_ui_action.js

Modal Framework: GlideModal

External Dependency: QrIckit API

Expected Server Side Script Include:
GenerateAssetQR — must return asset details when provided with a record sys_id.
(Not included in this PR; must exist on the instance. A Sample code is given)

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]

looks good to me