align image names with rhub

[j-i-l]

We are using a deprecated naming scheme and aligning it somewhat inconsistently to the actual r-hub containers:

r-containers/.github/workflows/create-publish-docker.yml

Lines 110 to 134 in 9360451

	# Map debian combinations
	if [[ "$TARGET_OS" == "debian" ]]; then
	if [[ "$COMPILER" == "clang" && "$R_VERSION" == "devel" ]]; then
	RHUB_IMAGE="ubuntu-clang"
	elif [[ "$COMPILER" == "gcc" && "$R_VERSION" == "devel" ]]; then
	RHUB_IMAGE="ubuntu-gcc12"
	elif [[ "$R_VERSION" == "release" ]]; then
	RHUB_IMAGE="ubuntu-release"
	elif [[ "$R_VERSION" == "patched" ]]; then
	RHUB_IMAGE="ubuntu-next"
	fi
	# Map fedora combinations
	elif [[ "$TARGET_OS" == "fedora" ]]; then
	# Note: R-hub doesn't have direct fedora equivalents for primary CRAN containers
	# Map to closest Ubuntu equivalents or specific Fedora containers
	if [[ "$COMPILER" == "gcc" && "$R_VERSION" == "devel" ]]; then
	RHUB_IMAGE="gcc15" # Use Fedora-based gcc15 container
	elif [[ "$COMPILER" == "clang" && "$R_VERSION" == "devel" ]]; then
	RHUB_IMAGE="gcc15" # No Fedora clang equivalent, use Fedora gcc15
	echo "Warning: No direct Fedora clang equivalent on r-hub, using gcc15"
	fi
	# Map valgrind
	elif [[ "$TARGET_OS" == "valgrind" ]]; then
	RHUB_IMAGE="valgrind"
	fi

By aligning our container naming with the r-hub sources the setup should become clearer.

[j-i-l]

it seems fs needs libuvl, tries (and fails) to build it locally. We install libuvl directly. If cmake is available then fs should succeed.

[j-i-l]

there seems to be an issue with the installation of fs. it seems to always attempt to build libuvl, even if it is already available on the system. This looks like a bug...

for us we can simply promote the cmake install and 'fs' build.

[j-i-l]

the fedora-gcc-devel container is failing because of rlang:

https://github.com/furrer-lab/r-containers/actions/runs/24400424277/job/71269219709?pr=61#step:6:7159

this seems to be an inconsistency between fedora and the r development version, nothing on our table.
For now we simply allow this container to fail silently.