Feature/field styles

[HackoDev1530]

PR Description: Apply the field style to the field on the form.

Pull Request Checklist

Overview

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

Code Quality

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

Repository Structure Compliance

• [x ] 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/
• [x ] I've used appropriate sub-categories within the top-level categories
• [x ] 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

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

[am-shakeel]

Hello @HackoDev1530,

Thanks for your submission. As we have already had similar ones.

As a reminder, please note:

Quality Over Quantity: Low-effort or spam pull requests will be marked accordingly.
Expanded Snippets: Code snippets reused from the ServiceNow Documentation or API References are acceptable only if they are expanded in a meaningful way (e.g., with additional context, documentation, or variations). Remember: "QUANTITY IS FUN, QUALITY IS KEY."

For Hacktoberfest, we’re aiming for high-quality contributions providing real-world use developer cases.

You can check some of the recently merged code snippets for reference. They are good examples of what we're aiming for.
I will close this PR, but feel free to create a new PR.