4.4.6 breaks Search API drive Views using VBO

Problem/Motivation

Hi, we have been running this wonderful module for years using custom Actions and even supporting Faceting for Views that are driven by the Drupal Search API (in specific Solr). Last working version for us was 4.4.5. 4.4.6 breaks any support
by Removing:

    if (!\method_exists($this->view->query, 'addWhere')) {
      throw new \Exception(\sprintf('Unsupported query type: %s', $this->view->query::class));
    }
    $this->view->query->addWhere('views_bulk_operations', $base_field_alias, $base_field_values, 'IN');

    // Rebuild the view query.
    $this->view->query->build($this->view);

and adding

@@ -358,6 +354,16 @@ class ViewsBulkOperationsActionProcessor implements ViewsBulkOperationsActionPro
    // query. Give those modules the opportunity to alter the query again.
    $this->view->query->alter($this->view);

    if (!($this->view->build_info['query'] instanceof SelectInterface)) {
      throw new \Exception(\sprintf('Unsupported query type: %s', $this->view->query::class));
    }

    // Add the IN condition directly to the built DB query rather than via
    // addWhere(). Using addWhere() is unreliable here because the type of
    // conjunction (OR or AND) relies on many factors regardless of the filter
    // group used. The SelectQuery root condition is always AND.
    $this->view->build_info['query']->condition($base_field_alias, $base_field_values, 'IN');

I understand the optimization, but reall, this breaks 32 sites we have! I wonder if you would accept a pull that checks if
$this->view->build_info['query'] exists ... IF not, goes back to the previous check using a `addWhere`, if there (SQL views) runs the 'IN' Condition?

This is the specific commit https://git.drupalcode.org/project/views_bulk_operations/-/commit/513b37...

Steps to reproduce

Upgrade to 4.4.6
Use VBO in a Search API driven View

Proposed resolution

Make the optimization an optional without breaking the fact this Module uses most logic on the underlaying Views logic and not the Plugin that drives the data

Remaining tasks

Get feedback

User interface changes

API changes

Data model changes

Thanks a lot!