Incorrect data type used for AMF Set ID (uint8 instead of uint16) Causing “No Matching AMF Found” Warning

🐞 Issue Description:

During UE RRC Reestablishment, the AMF Set ID is defined/used as a uint8 type in function ngap_gNB_nnsf_select_amf_by_amf_setid.

However, according to 3GPP specifications, the AMF Set ID is a 10-bit field, which requires at least a uint16 type for correct representation.

This mismatch can cause incorrect behavior when the AMF Set ID exceeds 255 (the maximum value for uint8).

In such cases, the gNB fails to match the AMF information, leading to warnings like

No matching AMF found for PLMN (MCC=%03d MNC=%0*d) and AMF SetID=%u