seem like at some point (spotted on release 2024.2) the arch value in the unified package was move to the end of the filename which cause ccm to select the wrong arch file
ccm had a fallback to support older version (4.3 and below) unified package that doesn't mention arch at all (before we had ARM support)
this change is catering to both options, but makeing sure all of the possible options are considered, correctly.
seem like at some point (spotted on release 2024.2) the arch value in the unified package was move to the end of the filename which cause ccm to select the wrong arch file
ccm had a fallback to support older version (4.3 and below) unified package that doesn't mention arch at all (before we had ARM support)
this change is catering to both options, but makeing sure all of the possible options are considered, correctly.