Fixed #13372: Put guard around assigning location via LDAP

[uberbrady]

A customer [fd-37146] also noticed some errors around LDAP syncs, where if they set no default location at all, the sync returns an error. This puts in a simple tristate to only try to retrieve the ID of the location if the location is not null.

I did a local edit on the customer instance to see if this fix actually does fix the problem and it seems to.

fixes #13372

[what-the-diff]

PR Summary

• User Location Handling Update
  The code was updated to ensure that if there is no specified location for a user, the system will now correctly identify and register it as 'Unspecified' (Null). This happens in a part of our system that syncs user data.

[mihaiolimpiu]

Careful, the fix I posted in the mentioned issue was wrong, will update.

Edit: I installed the current fix and this does not import any location.
Ideally we should import only the locations for the user from LDAP and if location is NULL, ignore.

What happens now, all users have a NULL location :( and ALWAYS updates all users.

[mihaiolimpiu]

Commits on Apr 25, 2023
added ldap_location to settings

@uberbrady: Retested everything, my comment above was based on the wrong impression that my users were having a location assigned automatically by mistake.

Restored a backup and... well realized my mistake. code looks good.

Thank you!

[lerroot]

What version of snipeIT will this fix be incorporated into?

[uberbrady]

Should be merged to master in the next week or so, and then when we cut a new point-release it should include the fix.