Update Azure Linux 3.0 RID mapping

[richlander]

Note

This PR was AI/Copilot-generated.

Summary

Update the layout RID normalization to key off Azure Linux 3.0 instead of the old Mariner 2.0 RID string while continuing to map to the existing cm.2 runtime assets.

• replace the stale mariner.2.0 string match with azurelinux.3.0
• keep the existing cm.2 runtime RID normalization behavior

Follow-up to dotnet/runtime#126528.

[Copilot]

Pull request overview

This PR updates the layout build RID normalization logic to recognize Azure Linux 3.0 RIDs (instead of the older Mariner 2.0 string) while still mapping runtime asset selection to the existing cm.2 RID.

Changes:

• Update the NetRuntimeRid normalization check from mariner.2.0 to azurelinux.3.0.
• Preserve the normalization target to cm.2 for runtime asset compatibility.

[Copilot]

The condition is based on NetRuntimeRid, but the replacement is applied to HostRid. If NetRuntimeRid is set explicitly (e.g., for cross/target layout generation), this will overwrite it with a value derived from the host RID (and potentially the host architecture), which can produce an incorrect runtime RID. Consider applying the replacement to $(NetRuntimeRid) (or, if the intent is host-only normalization, make the condition check HostRid.StartsWith(...) as well) so the same RID is used consistently.

Suggested change

	<NetRuntimeRid Condition="'$(DotNetBuild)' != 'true' and $(NetRuntimeRid.StartsWith('azurelinux.3.0'))">$(HostRid.Replace('azurelinux.3.0', 'cm.2'))</NetRuntimeRid>
	<NetRuntimeRid Condition="'$(DotNetBuild)' != 'true' and $(NetRuntimeRid.StartsWith('azurelinux.3.0'))">$(NetRuntimeRid.Replace('azurelinux.3.0', 'cm.2'))</NetRuntimeRid>