[ISSUE] Updating `databricks_mws_workspaces`.`workspace_name` causes `workspace_host` not to propagate changes to provider defined in the same root

[nfx]

trafficstars

Configuration

provider "databricks" {
  alias      = "account"
  host       = module.defaults.account_console
  account_id = module.defaults.databricks_account_id
  username   = data.azurerm_key_vault_secret.username.value
  password   = data.azurerm_key_vault_secret.password.value
}

...

resource "databricks_mws_workspaces" "this" {
  provider       = databricks.account
  account_id     = module.defaults.databricks_account_id
  aws_region     = module.defaults.aws_region
  workspace_name = "${local.prefix}-workaround"

  credentials_id           = databricks_mws_credentials.this.credentials_id
  storage_configuration_id = databricks_mws_storage_configurations.this.storage_configuration_id
}

provider "databricks" {
  alias    = "workspace"
  auth_type = "basic"
  host     = databricks_mws_workspaces.this.workspace_url
  username = data.azurerm_key_vault_secret.username.value
  password = data.azurerm_key_vault_secret.password.value
}

change workspace_name to other one.

Expected Behavior

Plan goes on, no error. Change in workspace_name forces replacement.

Actual Behavior

workspace provider doesn't see workspace_url and can't authenticate itself. Error.

This issue is to figure out if this is a provider bug or terraform bug.