Update Webform from 6.1.3 to 6.1.4 ( ~6.1.0 ) and remove committed patches

✅ Released varbase_core-9.0.43

✅ Released varbase_core-9.0.44
Removed the patch.
Faced issue with composer not getting latest commit changes on packages from https://packages.drupal.org/8

https://twitter.com/drupal_infra/status/1613594516958904320

http://Git.drupalcode.org is experiencing 'Geo' replication lag, which is resulting in composer and CI failures for Merge Requests, delayed d.o issue updates, etc. We are working to find a resolution, and have filed an upstream issue with
@gitlab
: https://gitlab.com/gitlab-org/gitlab/-/issues/387980

Geo verification not keeping up
For the last few weeks, repositories and wikis verifications on our geo secondary for git.drupalcode.org have been gradually falling behind.

I think this may have started with the 15.5 to 15.6.1 upgrade. Since the falling behind was very gradual, and it was over the holidays, I was monitoring but did not take any measures to correct it.
Around this upgrade, we stabilized our upgrade process, stopping sidekiq processes early before the upgrade, so long-running jobs can complete in time. We also aligned our upgrade process with the current instructions https://docs.gitlab.com/ee/administration/geo/replication/upgrading_the_...
After upgrading to 15.7.2, what we are currently running, verifications have fallen further behind, losing maybe a percent a day.
/admin/geo/sites reports all instances are healthy.
The primary site's verifications have been 99.9% or higher.
sudo gitlab-rake gitlab:geo:check reports everything is good on both primary and secondary sites.
On the secondary geo site:
In the tuning settings, we doubled the verification concurrency limit 3 times, currently to 800
We added a second Sidekiq process, both having 20 threads. We have not seen any Sidekiq backlog.
It does not appear resource constrained, CPU usage is 10% or less, load average 2-3, ~50% free memory.
We have 86,500 repositories.
I've reviewed https://docs.gitlab.com/ee/administration/geo/replication/troubleshootin... and haven't spotted anything helpful for our situation.
None of these measures seem to have had much of an effect on the secondary's verification queue, it is still gradually falling further behind.

I'd like recommendations for finding potential underlying issues, and ways to get verification caught up.

✅ Released varbase-9.0.11