rabbitmq: Remove consumer timeout to give long workers the time to do their job

Some origins can take several days to be ingested (svn, ...) so the default 30mn timeout is way to small.

Related to swh/infra/sysadm-environment#5595 (closed)

Click to expand

diff origin/production/saatchi.internal.softwareheritage.org current/saatchi.internal.softwareheritage.org
*******************************************
  File[/etc/rabbitmq/rabbitmq.config] =>
   parameters =>
     content =>
      @@ -12,4 +12,5 @@
           ]},
           {tcp_listeners, [{"0.0.0.0", 5672}]},
      +    {consumer_timeout, undefined},
           {vm_memory_high_watermark, 0.6},
           {default_user, <<"guest">>},
*******************************************
*** End octocatalog-diff on saatchi.internal.softwareheritage.org
*** Running octocatalog-diff on host scheduler0.internal.staging.swh.network
I, [2025-03-05T17:31:52.955434 #761540]  INFO -- : Catalogs compiled for scheduler0.internal.staging.swh.network
I, [2025-03-05T17:31:53.160111 #761540]  INFO -- : Diffs computed for scheduler0.internal.staging.swh.network
diff origin/production/scheduler0.internal.staging.swh.network current/scheduler0.internal.staging.swh.network
*******************************************
  File[/etc/rabbitmq/rabbitmq.config] =>
   parameters =>
     content =>
      @@ -12,4 +12,5 @@
           ]},
           {tcp_listeners, [{"0.0.0.0", 5672}]},
      +    {consumer_timeout, undefined},
           {vm_memory_high_watermark, 0.6},
           {default_user, <<"guest">>},
*******************************************
*** End octocatalog-diff on scheduler0.internal.staging.swh.network