see if airgap rpm deployment really needs distinction for standard/noarch/source #106
Description
This makes things more complicated and introduces a dimension in possible download URLs and installation commands.
E.g. in bundling.
E.g. in provisioning (we could be avoiding wild card *.rpm.
These rpm package variants all seem to contain the same content, byte for byte, as published on redpanda repos. So what's the point (that's the thought that prompted this issue).