Implement GUID/UUID handling Phase 4: OpenLDAP entryUUID support

[JayVDZ]

Summary

Follow-up work from #300 to complete the GUID/UUID handling strategy for OpenLDAP.

Phase 4: Add OpenLDAP entryUUID support

• OpenLDAP's entryUUID is a string attribute (RFC 4530), not binary
• Use IdentifierParser.FromString() for parsing
• Implement when OpenLDAP connector work begins

Prerequisites

• OpenLDAP connector implementation

OpenLDAP Integration Test Infrastructure

OpenLDAP is being introduced into the JIM integration test ecosystem as part of #72 (partition-scoped imports). That issue establishes the multi-suffix OpenLDAP configuration in docker-compose.integration-tests.yml and creates the population/test scaffolding. Once that infrastructure is in place, this issue can build on it without duplicating the setup work.

Related

• Closes phase 4 of Implement GUID/UUID handling strategy for cross-platform connector safety #300
• OpenLDAP integration test infrastructure established in Confirm if a partition is needed/relevant for a Full Sync? #72

[JayVDZ]

Phase 4 (OpenLDAP entryUUID string parsing) is complete:

• IdentifierParser.FromString() in src/JIM.Utilities/IdentifierParser.cs handles OpenLDAP's string UUID format (RFC 4530), with explicit documentation referencing OpenLDAP entryUUID.
• src/JIM.Connectors/LDAP/LdapConnectorRootDse.cs declares entryUUID as AttributeDataType.Text for OpenLDAP/Generic directories, while objectGUID remains AttributeDataType.Guid for AD/Samba.
• OpenLDAP integration test infrastructure is in place (Confirm if a partition is needed/relevant for a Full Sync? #72).

Phase 5 (cross-connector round-trip integration tests) has been moved to TetronIO/JIM-Brain#22 to track separately once SCIM/Database connectors land.