Add Company attribute to HR datasource and sync to Active Directory

[JayVDZ]

Summary

Add a new "Company" attribute to the HR CSV datasource that flows through the synchronisation rules to Active Directory user objects.

Description

The HR datasource (CSV) currently lacks a Company attribute. This is a standard Active Directory user attribute that should be provisioned from the HR system. Users should have their company affiliation synchronised from the HR source to their AD user objects.

Requirements

HR Datasource (CSV)

• Add a "company" column to the HR CSV test data generation
• Populate with realistic company names for test data
• Ensure consistent data across all template sizes (Nano through XXLarge)

Synchronisation Rules

• Add "company" to the inbound sync rule (HR → Metaverse)
  • Source: company (from CSV)
  • Target: company (metaverse attribute)
  • Type: Direct mapping
• Add "company" to the outbound sync rule (Metaverse → AD)
  • Source: company (metaverse attribute)
  • Target: company (AD attribute)
  • Type: Direct mapping

Test Data

• Update Populate-SambaAD.ps1 to handle company attribute if needed
• Update Generate-TestCSV.ps1 to include company names in CSV generation
• Ensure test data is realistic and consistent

Acceptance Criteria

• Company column added to HR CSV with realistic values
• Inbound sync rule includes company attribute mapping
• Outbound sync rule includes company attribute mapping
• Test data generation works for all templates
• Integration tests pass with company attribute flows working end-to-end
• Company attribute visible on user profiles in AD after sync

Related Issues

• Integration testing framework (#173)
• Scenario 1: HR to Enterprise Directory (referenced in INTEGRATION_TESTING.md)

Test Scenario

This will be validated through Scenario 1 (HR to Enterprise Directory):

1. HR CSV includes company values
2. Users imported from CSV with company attribute
3. Attribute flows to AD through sync rule
4. Company visible on AD user object after export