Don't produce CBL-Mariner 1/2-specific packages

[jkoritzinsky]

We don't ship these any more, so we can stop producing them.

Instead, produce a special .azl.rpm copy that's not versioned with Azure Linux (to avoid having to update this regularly) that has a configuration in Arcade to be signed with the correct certificate.

Contributes to #15486

To double check:

• The right tests are in and the right validation has happened. Guidance: https://github.com/dotnet/arcade/blob/main/Documentation/Validation.md

[NikolaMilosavljevic]

I thought these packages targeted Mariner and maybe Azure Linux as well. The process was to sign these and push to PMC. @mmitche @leecow

[jkoritzinsky]

For AzureLinux 3, we're just using the regular RPM packages we produce (which are identical to what we did for the CBL-Mariner packages as they're just copies).

We aren't going to publish new packages for Mariner 1 or 2 as 1 is already out of support and 2 is going out of support before .NET 10 comes out.

[NikolaMilosavljevic]

For AzureLinux 3, we're just using the regular RPM packages we produce (which are identical to what we did for the CBL-Mariner packages as they're just copies).

We aren't going to publish new packages for Mariner 1 or 2 as 1 is already out of support and 2 is going out of support before .NET 10 comes out.

Different signing certificate was used for Mariner/AzureLinux. Not sure how that's going to work with a single package, but some changes would be needed on the signing side - @mmitche

[jkoritzinsky]

@NikolaMilosavljevic if we just need AzureLinux vs regular PMC, I can change this to instead generate one general AzureLinux package variant.

[NikolaMilosavljevic]

@NikolaMilosavljevic if we just need AzureLinux vs regular PMC, I can change this to instead generate one general AzureLinux package variant.

I think that should work. Release process might need to be adjusted though - @leecow @rbhanda

[leecow]

I presume we want to continue publishing .NET 8 for Mariner 2 until 8 is out of support?

[jkoritzinsky]

I've updated this PR to instead change the naming of the files and integrate more directly with the Arcade SDK's signing support.

I presume we want to continue publishing .NET 8 for Mariner 2 until 8 is out of support?

I'm not planning on backporting this change to .NET 8 as of now, but I wouldn't expect us to publish packages for Mariner 2 after Mariner 2 is EOL (this June, not next June).

[NikolaMilosavljevic]

Looks fine to me, as long as this was validated offline in package/installer build.

@mmitche for awareness of the signing change.