Add CR configs for images

[yselkowitz]

What does the ELN SIG need to do?

• There have been various inquiries of late as to size and package minimization of RHEL images. We haven't focused on this much in quite a while, but this is something that CR is very capable of doing. Configs for the various image types should be added in order to track this.

This would appear to also need a fix for the size chart in workload config pages.

[tdawson]

Starting work on this.
Since this is for RHEL image, I am going to do my initial lists using the packages lists from ImageBuilder.

• Azure: CVM (x86_64)
• Azure: Plain (x86_64)
• AWS: HA (x86_64)
• AWS: Plain (aarch64, x86_64)
• QCOW2 (aarch64, ppc64le, s390x, x86_64)
• WSL (aarch64, x86_64)

Once those are in place, we'll work on some of the others built in different ways.

• UBI
• CentOS Stream Container: Base
• CentOS Stream Container: Minimum
• Azure: 3P (aarch64, x86_64)
• Azure: LVM (aarch64, x86_64)
• AWS: 3P (aarch64, x86_64)

[tdawson]

My first draft of the first six image configs is here:
minimization/content-resolver-input#1476

I'm a bit concerned about the names.
Mainly about aws vs ec2. The ImageBuilder names are ec2* , but the images that are built are aws*

[tdawson]

I've tracked down and I am quite confident I have all the packages requested to be in the 6 images I have. Right now I just keep going back and forth on the names of the files.

[tdawson]

Just one note incase it comes up later.
I only have two ec2 and azure image workloads, but there are several more images that are built.
First, I didn't so any of the SAP images. We don't have SAP packages in ELN, so I didn't make them.
Second, the other images have the same packages, just a different configuration and/or layout. They would look the same in Content Resolver.

[yselkowitz]

Done via minimization/content-resolver-input#1476 and minimization/content-resolver-input#1478. HA cleanup is waiting on #229.