Use the same tooling in community and product build

We should try hard to use the same build tooling in both builds. For example, same clang versions, openssl versions, etc.

This is so that our community build mimics the product build environment and we are not caught by surprises when doing the product build. In short, if it builds in community, it must also build fine in product.

This might be achieved by touching both sides. Example:

• Community base image could be the same (or the most similar possible) to the product one (ubi8?)
• Should we track the base image as a floating tag? Or should it be pinned? In other words, if we track a floating tag in both sides, then we should update it regularly, so they keep in sync.
• Should we pin to specific versions of packages (in both sides)? If so, we should make sure the versions are the same.