Added trim to import values

[snipe]

This just adds some trim() methods around the imported field values. We recently had a customer who ended up with duplicate statuses, since Ready to Deploy and Ready to Deploy are not the same string.

I'm not 100% sure I've gotten everything in this PR, but I'll keep testing.

[what-the-diff]

PR Summary

• Improvement of Data Input in Accessory Importer
  The change trims the model_number value before assigning it, resulting in cleaner, reliable, and standardized input data.

• Data Sanitization in Asset Importer
  Several fields (notes, image, requestable, warranty_months, byod) have been improved to provide accurate and error-free data by removing unwanted spaces before assignment.

• Enhancing Component Importer Process
  The changes ensure that the values for name and serial are trimmed before executing a query, providing greater accuracy and efficiency.

• Refining Consumable Importer
  Data input fields (name, model_number, item_no, min_amt) are now trimmed before assigning their values which promotes cleaner and standardized data.

• Updates to Item Importer
  This change enhances the data quality of Statuslabel and Manufacturer models by trimming the name field before saving, resulting in standardized and consistent data.

• Ensuring Better Data Input in License Importer
  An array of fields (asset_tag, expiration_date, license_email, license_name, maintained, purchase_order, order_number, manufacturer) will now be trimmed of excess spaces before assigning their values, leading to precise and standardized dataset.

• Improved Location Data through Location Importer
  This upgrade trims several fields (name, address, address2, city, state, country, zip, currency, ldap_ou, manager, manager_username, parent_location) before assignment or method execution, ensuring cleaner, more accurate location details.

• Efficiency Boost in User Importer
  All fields will now be trimmed before their values are assigned, cementing the uniformity and precision of user data.

[spencerrlongg]

Can't figure out any side effects of this, nor can I figure out a decent way to 'move it up a level' to avoid putting it on every line, so 👍

[marcusmoore]

There's a syntax error that needs to be fixed but other than that, I agree with Spencer's comments.