Support profile-defined SJRMT UNI storage

[GTTeancum]

Summary

• add optional profile fields for the SJRMT UNI payload offset and ring capacity
• preserve the existing 256-byte normalization when a profile does not opt in
• validate the profile-defined layout with a direct CRI DTX RPC test

Why

X-Men Legends initializes SJRMT UNI with a work area whose first 0x100 bytes are metadata and whose following 0x4000 bytes form the audio ring. Treating the whole request as the existing normalized 256-byte ring aliases metadata and payload storage. Keeping the layout profile-defined avoids changing established profiles while supporting this observed CRI variant.

Test plan

• cmake --build out/sjrmt-test --config Release --target ps2x_tests -- /m:1
• out/sjrmt-test/ps2xTest/Release/ps2x_tests.exe
• 426 passed, 0 failed