Fixed #11126: don't entitise custom CSS on the labels view

[trav-c]

Description

Update labels view to not entitise custom CSS as is already the case in all other views

Fixes #11126

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

• Generated HTML source review
  Added CSS containing double quotes and greater than signs and manually inspected the resulting (generate) HTML source code on the labels page to verify the custom CSS is not encoded
• Generated labels font
  Added custom CSS to use the slashed-zero variant of the "Inter" font for labels which requires the use of double quotes and verified that the CSS is correctly interpreted / rendered the browser

Test Configuration:

• PHP version: 8.1.6
• MySQL version: 5.6.51 (Percona Server)
• Webserver version: httpd-2.4.6-97.el7.centos.5.x86_64
• OS version: CentOS v7

Checklist:

• I have read the Contributing documentation available here: https://snipe-it.readme.io/docs/contributing-overview
• I have formatted this PR according to the project guidelines: https://snipe-it.readme.io/docs/contributing-overview#pull-request-guidelines
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• [] I have commented my code, particularly in hard-to-understand areas
• [] I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[welcome]

💖 Thanks for this pull request! 💖

We use semantic commit messages to streamline the release process and easily generate changelogs between versions. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix if it doesn't have one already.

Examples of commit messages with semantic prefixes:

• Fixed #<issue number>: don't overwrite prevent_default if default wasn't prevented
• Added #<issue number>: add checkout functionality to assets
• Improved Asset Checkout: use new notification method for checkout

Things that will help get your PR across the finish line:

• Document any user-facing changes you've made.
• Include tests when adding/changing behavior.
• Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

[welcome]

Congrats on merging your first pull request! 🎉🎉🎉