test: investigate SNOMED RF2 import in e2e tests

[kojiromike]

Summary

During local e2e testing, SNOMED RF2 imports report success but the sct2_description table remains empty. This may be a test environment issue or file structure mismatch, not necessarily a bug in the CLI tool.

Observed Behavior (Local Testing)

• File: SnomedCT_ManagedServiceUS_PRODUCTION_US1000124_20250901T120000Z.zip (642MB)
• Filename pattern matches correctly (detected as "Complete US Extension", RF2 format)
• Import completes in ~6 seconds (too fast for a 642MB file)
• Tracking table is updated with success
• sct2_description table has 0 rows

Possible Causes

• Downloaded SNOMED file may have different internal structure than expected
• OpenEMR's snomedRF2_import() may expect specific directory layout
• The file from NLM/UMLS may be packaged differently than what OpenEMR tested with

Investigation Needed

• Check what directory structure OpenEMR's snomedRF2_import() expects inside the archive
• Verify the downloaded file's internal structure
• Compare with OpenEMR's documented SNOMED import process
• Determine if this is a file sourcing issue vs a code issue

Test Environment

• OpenEMR: development-easy Docker
• CLI: oce-cli-import-codes
• SNOMED file source: NLM UMLS download

Notes

This was discovered during e2e test development. Other vocab imports (RXNORM, ICD10, CQM_VALUESET) work correctly in the same environment.