Conditionally update assets when user's location moves via LDAP

[uberbrady]

Fixes: [fd-45970]

We added code to change assets' locations if the user's location changes via LDAP. But the way the query was working, it would tweak the 'updated at' attribute on the user whether or not it actually changed the location of the asset in question. This was confusing for one of our customers in how they use the app.

Additionally, if a change was made, there wasn't going to be any log entry in the asset history to explain why it wasn't in the location that it had been before.

This fixes both problems - only making changes to the assets of the user if the user's location has actually changed, and making sure that it's a regular save() so that a log entry with an 'update' will still get created.

I tested this on our test LDAP server, setting the ldap_location attribute to physicaldeliveryofficename, and setting the 'Office' value of one of the users to one of our locations. Then I changed the user's location on my development environment, did a checkout of an asset to that user, then ran an LDAP sync. When I did that, the asset showed an 'update' action of it moving from the old location to the LDAP-based one.

[what-the-diff]

PR Summary

• Improved Asset Location Update Logic
  The system now monitors if a user's asset location ID has been altered, enhancing the accuracy of asset tracking.

• Individual Asset Location Updates
  Rather than updating all assets at once, the new code carefully goes through each asset and updates its location ID separately, potentially reducing errors or oversights in tracking.

• Potential for Enhanced Documentation of Asset Location Changes
  The team has proposed the idea of adding a note whenever an asset's location changes, showcasing future opportunities for improved traceability and record-keeping.