Fixes #13251 - ldap_location attribute

[uberbrady]

A customer [FD-36851] reports that his locations were being unset in his per-location-specific various LDAP syncs.

It seems like we'll override the Location that a user would be assigned if they were using the --location command-line option, even if the user had not configured the LDAP Location field.

This adds a guard clause that will only try to override the location if the field is being used.

[what-the-diff]

PR Summary

• Modification to LdapSync.php
  The LdapSync.php file within our application has been updated for enhanced functionality.

• Addition of conditional statement
  A new rule has been introduced that checks two things before proceeding - it verifies whether the 'ldap_result_location' setting is enabled and also if the item's location information isn't empty.

• Creation of Location entry
  Provided that our newly implemented conditions are met, the system will then proceed to create a fresh 'Location' entry utilizing the given location data.

• Advantages of the new changes
  This refined approach ensures that new Location entries are created more responsibly, conditioned on necessary prerequisites being satisfied, increasing the overall efficiency of our system. This means we avoid creating redundant or unnecessary Location entries, streamlining our data management.