Revise strategy to derive SHM name in data plane implementation

### What

Currently the name for SHM creation is derived from the uid + time since epoch.

During stress testing it was observed, that it seems that two SHM were attempted to be created with the same name resulting in an error.

`2026/09/09 14:05:34.2734517 241131987 000 ECU1 NONE shm log warn verbose 3 Cannot recreated Shared Memory /score_crypto_1000_1788962734516920255 as it's already been created.`

The stress tests did run for several minutes, only then the issue was observer. While it seems rare, it is possible to run into this issue.

Thus we may want to re-evaluate the approach how to derive the names

### Acceptance Criteria (DoD)

New strategy derived or current risk accepted.

### How

_No response_