Fix SCORM 2004 global objective parsing

[jcputney]

Summary

• preserve the SCORM 2004 default of objectivesGlobalToSystem=true while exposing whether the manifest explicitly supplied the attribute
• avoid treating an omitted default as explicit organization-level sequencing usage
• normalize percent-encoded XML whitespace in targetObjectiveID values used by global objective maps

Why

The ADL CTS OB-02b package encodes spaces in a global objective identifier. Preserving the decoded, normalized identifier is required for the LMS sequencing engine to address the same objective. The organization flag also needs both its specification default and presence information so downstream sequencing configuration can distinguish omission from an explicit value.

Verification

• ./mvnw -B -ntp clean verify -Dgpg.skip=true
• 1,243 tests passed, including the bundled SCORM 2004 ADL CTS manifest sweep and LocalStack integration tests
• exact parser changes were exercised by the Phoenix standalone and browser SCORM CTS runs (78/78 each)

[github-actions]

📊 Benchmark Results

Triggered by workflow run.

Benchmark	Score	Error	Unit
🟢 detectModuleType	0.002	±0.000	ms/op
🟢 parseModule	1.786	±3.466	ms/op
🟢 detectModuleType	0.000	±0.000	ms/op
🟢 parseModule	0.105	±0.378	ms/op
🟢 detectModuleType	0.220	±0.409	ms/op
🟢 parseModule	0.642	±2.018	ms/op
🟢 detectModuleType	0.174	±0.314	ms/op
🟢 parseModule	1.666	±7.473	ms/op

✅ All benchmarks passed performance thresholds.