The big ISOs contain all packages, for smaller download use network install.
A nice review, thank you.
On the download sizes of 8GB (RHEL) and 7GB (Rocky and Alma), these are for the ISO images containing all packages. The sort of installation which might be done for a machine isolated from the internet. A typical installation doesn't select all packages, and so the installed operating system on disk is smaller than the distribution's ISO.
For a machine connected to the internet choose the "boot" image. Say the image Rocky-10.0-x86_64-boot.iso, which is 817MB. After writing this image to a USB and booting from it. select the "Network install" path through the installer. Only the packages required for the type of installation requested will be downloaded. Better still, it will download the most recent of the required packages, so there will be no large update required after the installation.
Network installs are important, as that is the way RHEL-family installations are done for the many hundreds of servers in server farms.
The essential difference is that corporate installs have the computer boot the "boot image" across the network using PXE and TFTP rather than from the USB. Then the "kickstarter" facility provides pre-canned answers to the network install. The network install typically uses a copy of the package repositories located on a web server within the organisation, rather than across the Internet to Rocky's servers.
The "kickstarter" approach also allows the equivalent to Window's "slipstreaming". Example Corp creates its own package, say examplecorp-server. That package lists as dependencies the organisation's baseline of packages to install. The second-last command in the kickstarter configuration installs examplecorp-server (and its automatically-determined dependencies); and the last command runs Ansible to apply the corporate configuration to packages. This technique has two nice outcomes: (1) the first boot of the machine into the new operating system has it fully up-to-date and fully-configured, there's no race against malware; (2) the machine is fully described in Git (where the DHCP, kickstarter, examplecorp-server.spec package definition, and Ansible configurations are maintained). Therefore the only data which needs to be backed up is user and service data, not umpteen copies of the operating system. It typically takes 20 minutes to automatically install and configure up a new server after it is powered on.