ci: update tag publish job to ubuntu-latest

Localiza el workflow de GitHub Actions que contiene el trabajo de publicación de tags y reproduce el fallo de tarantool-setup en Ubuntu 24.04. Actualiza el workflow según lo solicitado y, después, verifica que pueda ejecutarse sin publicar mientras sigue compilando rocks, y que la publicación de tags se complete correctamente.

It is unable to setup tarantool 2.10 with tarantool-setup on ubuntu-24.04:

  Preparing to unpack .../5-tarantool-common_2.11.6.g74ad6a412d-1_all.deb ...
  Unpacking tarantool-common (2.11.6.g74ad6a412d-1) ...
  dpkg: error processing archive /tmp/apt-dpkg-install-5Uw89m/5-tarantool-common_2.11.6.g74ad6a412d-1_all.deb (--unpack):
   unable to open '/usr/lib/systemd/system/tarantool.service.dpkg-new': No such file or directory
  No apport report written because the error message indicates an issue on the local system
  Selecting previously unselected package tarantool.
  Preparing to unpack .../6-tarantool_2.11.6.g74ad6a412d-1_amd64.deb ...
  Unpacking tarantool (2.11.6.g74ad6a412d-1) ...
  Selecting previously unselected package tarantool-dev.
  Preparing to unpack .../7-tarantool-dev_2.11.6.g74ad6a412d-1_amd64.deb ...
  Unpacking tarantool-dev (2.11.6.g74ad6a412d-1) ...
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-5Uw89m/5-tarantool-common_2.11.6.g74ad6a412d-1_all.deb
  needrestart is being skipped since dpkg has failed
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Error: The process '/usr/bin/sudo' failed with exit code 100
  /usr/bin/tarantool --version
  Tarantool 2.11.6-0-g74ad6a412d
  Target: Linux-x86_64-RelWithDebInfo
  Build options: cmake . -DCMAKE_INSTALL_PREFIX=/usr -DENABLE_BACKTRACE=TRUE
  Compiler: GNU-13.2.0
  C_FLAGS:-g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/build/tarantool-2.11.6=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/build/tarantool-2.11.6=/usr/src/tarantool-2.11.6.g74ad6a412d-1 -Wdate-time -D_FORTIFY_SOURCE=3 -fexceptions -funwind-tables -fasynchronous-unwind-tables -fno-common -fopenmp -msse2 -Wformat -Wformat-security -Werror=format-security -fstack-protector-strong -fPIC -fmacro-prefix-map=/build/tarantool-2.11.6=. -std=c11 -Wall -Wextra -Wno-gnu-alignof-expression -fno-gnu89-inline -Wno-cast-function-type
  CXX_FLAGS:-g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/build/tarantool-2.11.6=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/build/tarantool-2.11.6=/usr/src/tarantool-2.11.6.g74ad6a412d-1 -Wdate-time -D_FORTIFY_SOURCE=3 -fexceptions -funwind-tables -fasynchronous-unwind-tables -fno-common -fopenmp -msse2 -Wformat -Wformat-security -Werror=format-security -fstack-protector-strong -fPIC -fmacro-prefix-map=/build/tarantool-2.11.6=. -std=c++11 -Wall -Wextra -Wno-invalid-offsetof -Wno-gnu-alignof-expression -Wno-cast-function-type

Also, it would be a good idea always to run the workflow, but only build rocks without publishing. Because now the problems are discovered too late - when a tag is published.