CentOS: move gpg keys to repo files

Definition of 3rdparty repo can contain also url to gnupg key used to
sign files there.

DNF knows how to handle that so we do not need to import keys in base
image anymore.

Functionality stays as people may use own repos with own keys.

Change-Id: I88e8e86ca35ee1b6b6b5551c3ca8698f0ed814cb

docker/base/Dockerfile.j2

@@ -79,10 +79,6 @@ SHA1 keys are not supported in RHEL9: https://github.com/rpm-software-management
     'https://packages.grafana.com/gpg.key',
  #}
 {% set base_yum_repo_keys = [
-    'https://downloads.mariadb.com/MariaDB/RPM-GPG-KEY-MariaDB',
-    'https://packages.treasuredata.com/GPG-KEY-td-agent',
-    'https://github.com/rabbitmq/signing-keys/releases/download/2.0/rabbitmq-release-signing-key.asc',
-    'https://repos.influxdata.com/influxdb.key',
 ] %}
 
 {% if base_arch == 'x86_64' %}

docker/base/mariadb.repo

@@ -4,3 +4,4 @@ baseurl = https://dlm.mariadb.com/repo/mariadb-server/10.6/yum/rhel/$releasever/
 gpgcheck = 1
 enabled = 0
 module_hotfixes = 1
+gpgkey = https://downloads.mariadb.com/MariaDB/RPM-GPG-KEY-MariaDB

docker/base/rabbitmq_rabbitmq-erlang.repo

@@ -4,3 +4,4 @@ name=rabbitmq_rabbitmq-erlang
 baseurl=https://packagecloud.io/rabbitmq/erlang/el/8/$basearch
 gpgcheck=1
 enabled=0
+gpgkey = https://github.com/rabbitmq/signing-keys/releases/download/2.0/rabbitmq-release-signing-key.asc

docker/base/rabbitmq_rabbitmq-server.repo

@@ -3,3 +3,4 @@ name=rabbitmq_rabbitmq-server
 baseurl=https://packagecloud.io/rabbitmq/rabbitmq-server/el/8/$basearch
 gpgcheck=1
 enabled=0
+gpgkey = https://github.com/rabbitmq/signing-keys/releases/download/2.0/rabbitmq-release-signing-key.asc