Update Celery and Kombu links

doc/source/admin/galaxy_options.rst

@@ -4672,7 +4672,7 @@
     the process that handled that particular request will tell all
     others to also reload, lock jobs, etc. For connection examples,
     see
-    http://docs.celeryproject.org/projects/kombu/en/latest/userguide/connections.html
+    https://docs.celeryq.dev/projects/kombu/en/stable/userguide/connections.html
     Without specifying anything here, galaxy will first attempt to use
     your specified database_connection above.  If that's not specified
     either, Galaxy will automatically create and use a separate sqlite

doc/source/admin/mq.md

@@ -2,7 +2,7 @@
 # Message queue
 
 Galaxy uses a message queue internally for communicating between processes. 
-This is powered by the [Kombu MQ library](https://docs.celeryproject.org/projects/kombu/en/stable/). 
+This is powered by the [Kombu MQ library](https://docs.celeryq.dev/projects/kombu/). 
 For example, when reloading the toolbox or locking job execution,
 the process that handled that particular request will tell all others to also reload, lock jobs, etc. 
 
@@ -11,8 +11,8 @@ the process that handled that particular request will tell all others to also re
 <!-- TODO the types of messages being passed, more detailed than above -->
 
 This is configured via the [amqp_internal_connection](https://docs.galaxyproject.org/en/latest/admin/config.html#amqp-internal-connection)
-option in `galaxy.yml`. For connection examples, see the [Kombu connection documentation](https://docs.celeryproject.org/projects/kombu/en/stable/userguide/connections.html).
-See the [URL specification](https://docs.celeryproject.org/projects/kombu/en/stable/userguide/connections.html#urls) on that page for more information on configuring different transports.
+option in `galaxy.yml`. For connection examples, see the [Kombu connection documentation](https://docs.celeryq.dev/projects/kombu/en/stable/userguide/connections.html).
+See the [URL specification](https://docs.celeryq.dev/projects/kombu/en/stable/userguide/connections.html#urls) on that page for more information on configuring different transports.
 
 <!-- TODO copy in an actual rabbit MQ example from the link above 
 ```
@@ -29,7 +29,7 @@ database located in your <galaxy>/database folder.
 Kombu and Galaxy support a variety of MQ transport/server options. 
 [RabbitMQ](https://www.rabbitmq.com/) via AMQP is the most popular for production deployments.
 
-Visit the [Kombu reference index](https://docs.celeryproject.org/projects/kombu/en/latest/reference/index.html) for a
+Visit the [Kombu reference index](https://docs.celeryq.dev/projects/kombu/en/stable/reference/index.html) for a
 complete list of supported transports and their configuration.
 
 <!-- TODO Specify any requirements Galaxy has for transport features. -->

doc/source/releases/21.05_announce.rst

@@ -9,8 +9,8 @@ Highlights
 ===========================================================
 
 **New development stack**
-  Galaxy release 21.09 will ship with a new web framework (`fastAPI <https://fastapi.tiangolo.com/>`__),
-  `Celery <https://docs.celeryproject.org/en/stable/index.html>`__ task queue and process management using `Circus <https://circus.readthedocs.io/en/latest/>`__. You can preview new stack now by running ``APP_WEBSERVER=dev ./run.sh``.
+  Galaxy release 21.09 will ship with a new web framework (`FastAPI <https://fastapi.tiangolo.com/>`__),
+  `Celery <https://docs.celeryq.dev/>`__ task queue and process management using `Circus <https://circus.readthedocs.io/en/latest/>`__. You can preview new stack now by running ``APP_WEBSERVER=dev ./run.sh``.
 
 **Celery for background tasks**
   Galaxy can now run certain tasks in the background. The Celery workers are

doc/source/releases/22.01_announce.rst

@@ -11,7 +11,7 @@ Highlights
 **Galaxy starts as FastAPI application by default**
   Starting Galaxy via ``run.sh`` will use the new `gravity process manager
   <https://github.com/galaxyproject/gravity>`__.
-  The new configuration uses `gunicorn <https://gunicorn.org/>`__ and `FastAPI <https://fastapi.tiangolo.com/>`__ to drive Galaxy's web process and starts job handler and `Celery <https://docs.celeryproject.org/>`__ processes automatically.
+  The new configuration uses `gunicorn <https://gunicorn.org/>`__ and `FastAPI <https://fastapi.tiangolo.com/>`__ to drive Galaxy's web process and starts job handler and `Celery <https://docs.celeryq.dev/>`__ processes automatically.
   For more details and instructions please consult the `Migrating to Gunicorn documentation <https://docs.galaxyproject.org/en/latest/admin/migrating_to_gunicorn.html>`__.
   (`Pull Request 13224`_).
 

lib/galaxy/config/sample/galaxy.yml.sample

@@ -2307,7 +2307,7 @@ galaxy:
   # For example, when reloading the toolbox or locking job execution,
   # the process that handled that particular request will tell all
   # others to also reload, lock jobs, etc. For connection examples, see
-  # http://docs.celeryproject.org/projects/kombu/en/latest/userguide/connections.html
+  # https://docs.celeryq.dev/projects/kombu/en/stable/userguide/connections.html
   # Without specifying anything here, galaxy will first attempt to use
   # your specified database_connection above.  If that's not specified
   # either, Galaxy will automatically create and use a separate sqlite

lib/galaxy/config/schemas/config_schema.yml

@@ -3404,7 +3404,7 @@ mapping:
           example, when reloading the toolbox or locking job execution, the process
           that handled that particular request will tell all others to also reload,
           lock jobs, etc.
-          For connection examples, see http://docs.celeryproject.org/projects/kombu/en/latest/userguide/connections.html
+          For connection examples, see https://docs.celeryq.dev/projects/kombu/en/stable/userguide/connections.html
 
           Without specifying anything here, galaxy will first attempt to use your
           specified database_connection above.  If that's not specified either, Galaxy