Race condition with drupal.autocomplete and geocoder autocomplete

Problem/Motivation

I noticed that the exposed filter for proximity had the autocomplete working only sometimes.
While debugging putting breakpoints on the geocoder js code always resulted on the correct behavior but without breakpoints the geocoder js code runs first, sets an autocomplete on the input element then sets the "form-autocomplete" class which triggers the Drupal.behaviours.autocomplete and deletes the previous autocomplete configuration overwriting it with an invalid new one.

Removing the .addClass("form-autocomplete"); solves the issue but then I don't get styling for the input.

Note that the order of execution of Drupal behaviours AFAIK can't be determined .

Steps to reproduce

I am on Drupal 11.4.4
Configure a view with an exposed autocomplete origin.
Maybe you get the bug with that configuration but if not you can simulate the Drupal autocomplete behaviour running later than geocoder's with this dirty wait

Drupal.behaviors.autocomplete = {
    attach(context) {
      var sleep = function(ms){
        var waitUntil = new Date().getTime() + ms;
        while(new Date().getTime() < waitUntil) continue;
      };
      sleep(2000);
      // Act on textfields with the "form-autocomplete" class.
      once('autocomplete', 'input.form-autocomplete', context).forEach(
...

Proposed resolution

I'm not sure how avoid the autocomplete conflict. So far I'm patching geocoder to remove the .addClass("form-autocomplete"); line.

Remaining tasks

Come up with a solution

User interface changes

API changes

Data model changes