O3-5696: Fix Wrong ORM mapping, duplicate DB lookup & null crash

[UjjawalPrabhat]

Three independent backend defects in the queue module:

• QueueEntry.queueComingFrom used @OneToOne, implying each source queue belongs to a single entry. Many entries can transition from the same queue, so switch to @ManyToOne (matching queue/patient/visit/etc.).

• AbstractBaseQueueDaoImpl.get(uuid) executed its criteria query twice, discarding the first result. Drop the redundant call so each UUID lookup runs exactly one query (affects all queue DAOs via the base).

• QueueEntryResource.getDisplay null-checked personName but dereferenced a possibly-null patient first, throwing NPE on bad data rows and crashing the whole REST page. Null-check the patient and fall back to the queue entry UUID. Added a unit test for the null-patient case.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud