Hotfix: swap UIDs after RRCReestablishment

The CellGroup is created considering UID, for example: pucchres0->startingPRB = 8 + uid; and since we keep the CellGroup from the previous RNTI/UID we should keep also the previous UID.

Considering the scenario where a UE did successful RRCReestablishment, it was getting uid = 1, and uid = 0 was removed. When another UE connected, it was getting UID = 0 (because 0 was already free), and so the PUCCH 0 resource was conflicting with the first UE.

This MR fixes these messages when a new UE connects after a first one did successful RRCReestablishment:

[NR_MAC]    879.15 VRB MAP in  880. 4 not free. Can't schedule CSI reporting on PUCCH.
[NR_MAC]    879.15 VRB MAP in  880. 4 not free. Can't schedule CSI reporting on PUCCH.
[NR_MAC]    879.15 VRB MAP in  880. 4 not free. Can't schedule CSI reporting on PUCCH.
[NR_MAC]    879.15 VRB MAP in  880. 4 not free. Can't schedule CSI reporting on PUCCH.
[NR_MAC]    879.15 VRB MAP in  880. 4 not free. Can't schedule CSI reporting on PUCCH.
[NR_MAC]   Cannot schedule SR. PRBs not available
[NR_MAC]   Cannot schedule SR. PRBs not available
[NR_MAC]   Cannot schedule SR. PRBs not available
[NR_MAC]   Cannot schedule SR. PRBs not available
[NR_MAC]   Cannot schedule SR. PRBs not available
[NR_MAC]   Cannot schedule SR. PRBs not available
[NR_MAC]   Cannot schedule SR. PRBs not available
[NR_MAC]    883.14 VRB MAP in  884. 3 not free. Can't schedule CSI reporting on PUCCH.
[NR_MAC]    883.14 VRB MAP in  884. 3 not free. Can't schedule CSI reporting on PUCCH.
[NR_MAC]    883.14 VRB MAP in  884. 3 not free. Can't schedule CSI reporting on PUCCH.
[NR_MAC]    883.14 VRB MAP in  884. 3 not free. Can't schedule CSI reporting on PUCCH.
[NR_MAC]    883.14 VRB MAP in  884. 3 not free. Can't schedule CSI reporting on PUCCH.
[NR_MAC]    883.14 VRB MAP in  884. 3 not free. Can't schedule CSI reporting on PUCCH.