In CRW-2644, we set up a GHA to publish CRW plugin registry content per architecture to GH pages.

Plugin registry published to https://redhat-developer.github.io/codeready-workspaces/che-plugin-registry/2.16/x86_64/v3/plugins/
Plugin registry published to https://redhat-developer.github.io/codeready-workspaces/che-plugin-registry/next/x86_64/v3/plugins/
Plugin registry published to https://redhat-developer.github.io/codeready-workspaces/che-plugin-registry/2.16/ppc64le/v3/plugins/
Plugin registry published to https://redhat-developer.github.io/codeready-workspaces/che-plugin-registry/next/ppc64le/v3/plugins/
Plugin registry published to https://redhat-developer.github.io/codeready-workspaces/che-plugin-registry/2.16/s390x/v3/plugins/
Plugin registry published to https://redhat-developer.github.io/codeready-workspaces/che-plugin-registry/next/s390x/v3/plugins/

But now that we've dropped openj9 support (CRW-2729, CRW-2750) and use the same udi container for all arches' sidecar needs, we maybe don't need to have 3 identical copies of the registry yaml pushed to GH pages.

So, for consideration: should we simplify back down to a single published registry? Or keep the option to have differences between the arches, eg., for dotnet or fuse-jdk8 support on only x64?