Drush Cron run is verbose after update

Problem/Motivation

After upgrading from 3.0.5 to 3.1.6 performing a drush cron shows the following message every single time:

*   Trying 0.000.00.000:443...
* Connected to server.name (0.000.00.000) port 443 (#0)
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: CN=*.server.name
*  start date: Feb 23 00:00:00 2023 GMT
*  expire date: Jul 20 23:59:59 2023 GMT
*  issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M02
*  SSL certificate verify ok.
> GET /solr/server.name/select?omitHeader=true&wt=json&json.nl=flat&q=%2A%3A%2A&start=0&rows=1&fl=%2A%2Cscore&json.facet=%7B%22maxVersion%22%3A%22max%28_version_%29%22%7D&request_id=(random_id) 7 HTTP/1.1
Host: server.name
Cookie: acquia_solr_time=random_time; acquia_solr_nonce=(random_string); acquia_solr_hmac=(random_string);
User-Agent: acquia_search/3.1.6
Content-Type: application/x-www-form-urlencoded; charset=utf-8

* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Mon, 20 Mar 2023 14:17:34 GMT
< Content-Type: application/json;charset=utf-8
< Content-Length: 1756
< Connection: keep-alive
< Pragma: hmac_digest=random_string;
< Vary: Origin
< 
* Connection #0 to server.name left intact

Steps to reproduce

Run drush cron

Proposed resolution

Is this normal? if so, can we disable this? If not, can we be a bit clearer about why this is coming up?

I noticed that there is a message about updating to 3.0.9 before updating to 3.0+ but I only saw that after upgrading. I don't seen any documented reason for this to be necessary, so I am not sure if this is due to the upgrade process.

Please advise.