Fixed: escape '/' in preg_quote of asset tag prefix

[mrdahbi]

This resolves the issue I encountered in version 8 of snipe-it (8.0.4)

When using a prefix with forward slash, preg_quote without arguments fails to escape it and results in error in Javascript console while trying for example to create a new asset.

Here's the original error:
missing after parenthesis Uncaught SyntaxError: missing ) source: create:1303:64
which points to the same line fixed in edit.blade.php

[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.

[what-the-diff]

PR Summary

• Improved JavaScript Function Accuracy
  The update to the JavaScript function allows it to process additional information, improving the accuracy of its tasks. The specific change involves the addition of a second parameter in a technical process called preg_quote, ensuring any automatically added prefixes are properly recognized and handled. This means our software will behave more predictably and cleanly when dealing with sequences generated by the system.

[snipe]

Hi there - thanks for this! Can you please re-target this PR to point to the develop branch, per our Contributing documentation?

You usually don't need to close and re-open. After you create a pull request, you can modify the base branch so that the changes in the pull request are compared against a different branch. By changing the base branch of your original pull request rather than opening a new one with the correct base branch, you’ll be able to keep valuable work and discussion.

Thanks!