Convert Form::textarea to blade component

[marcusmoore]

This PR introduces the <x-input.textarea> blade component and uses it to replace Form::textarea usage in our blade templates.

---

Pages Affected

• Categories
  • https://snipe-it.test/categories/create
  • https://snipe-it.test/categories/1/edit
• Custom Fields
  • https://snipe-it.test/fields/create
  • https://snipe-it.test/fields/1/edit : has to been a list box element
• Settings
  • https://snipe-it.test/admin/branding
  • https://snipe-it.test/admin/settings
  • https://snipe-it.test/admin/ldap
  • https://snipe-it.test/admin/saml

Modals Affected

• Upload file modals like on https://snipe-it.test/hardware/1#files

---

Extracted via copy/paste from #15983.

[what-the-diff]

PR Summary

• Introduction of a New Text Area Component
  This PR focuses on the introduction of a new text area component to the Blade file, simplifying existing codes and making it more reusable for future needs.

• Updated Usage of New Text Area Component
  Replacing the previous Form::textarea with the newly-created <x-input.textarea> component, this update provides greater consistency in multiple files including, but not limited to:

  • 'Edit Fields' section in custom fields
  • EULA text area in category edit form
  • Notes input in file upload modal
  • Custom CSS and footer text inputs in branding settings
  • Default EULA text in general settings
  • LDAP TLS key and cert fields in LDAP settings
  • SAML settings inputs in SAML settings

These changes promote a uniform implementation of the text area component, thus making the platform more synchronized and manageable.