Enabling module triggers a separate core bug related to views filters

Oh interesting. I had not looked very closely at the code of this module before using it.

foreach ($field_configs as $field_config) {
    $table_name = $field_config->getTargetEntityTypeId() . '__' . $field_config->getName();
    $column_name = $field_config->getName() . '_target_id';
    if (
      isset($data[$table_name][$column_name]['filter']['id'])
      && in_array($data[$table_name][$column_name]['filter']['id'], ['numeric', 'string'])
    ) {
      $data[$table_name][$column_name]['filter']['id'] = 'entity_reference';
    }
  }

That changes the filter from a numeric string to a entity reference for all instances within views, but that's sort of a mismatch for any existing view. I'm not really sure this could be done in a way that doesn't break backwards compatibility unless enabling the module recursively updated every view with an existing entity reference filter.