Fixed Ldap sync field clear bug

[Godmartinz]

Description

If an LDAP settings field was left blank for a sync it would null the existing users' matching fields. This applies a check on the ldap settings options itself.

Fixes #13373

Type of change

Please delete options that are not relevant.

• [ x] Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Test Configuration:

• PHP version:
• MySQL version
• Webserver version
• OS version

Checklist:

• I have read the Contributing documentation available here: https://snipe-it.readme.io/docs/contributing-overview
• I have formatted this PR according to the project guidelines: https://snipe-it.readme.io/docs/contributing-overview#pull-request-guidelines
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[what-the-diff]

PR Summary

• Enhancements in Data Handling
  The update enforces checks for empty data before feeding user information from LDAP server into our system. This results in cleaner data management, by preventing potential interruptions due to missing or null values.

[snipe]

Thanks for this :) Two quick things - looks like we have a merge conflict here - can you handle that? Second, is it a possible scenario that we'd end up with a blank value vs null?

[snipe]

Ping @Godmartinz

[Godmartinz]

Ah! sorry, Conflicts are fixed. You brought up a good point about blank space. there shouldn't be any spaces allowed, before, in between, or after. going to add some validation for this in another PR against the livewire changes.

[Godmartinz]

@snipe as mentioned in the dev meet yesterday, i posted a separate PR that trims whitespace off an values for the ldap attributes. You could technically put a blank in for any field, but it would not sync anything if you did.