Modifying Space Id on an existing environment doesn't cause a replacement

[tleed5]

Describe the bug
Modifying the space_id on an environment resource doesn't trigger a replacement but Terraform instead tries to update the resource in place which fails with

│ Error: Octopus API error: Resource is not found or it doesn't exist in the current space context. Please contact your administrator for more information. []
│   with octopusdeploy_environment.env,
│   on main.tf line 37, in resource "octopusdeploy_environment" "env":
│   37: resource "octopusdeploy_environment" "env" {

Steps to reproduce

1. Apply this TF

resource "octopusdeploy_space" "space" {
  name                 = "test space"
  space_managers_teams = ["teams-everyone"]
}

resource "octopusdeploy_environment" "env" {
  name     = "Env 1"
  space_id = octopusdeploy_space.space.id
}

2. Update the TF to and re-apply

resource "octopusdeploy_space" "new_space" {
  name                 = "new test space"
  space_managers_teams = ["teams-everyone"]
}

resource "octopusdeploy_environment" "env" {
  name     = "Env 1"
  space_id = octopusdeploy_space.new_space.id
}

Expected behavior
Modifying the space_id on the environment triggers a replacement of the resource

Logs and other supporting information
Add the output of running tf plan or tf apply along with any errors in the Octopus Server logs.

Additional context
Work around - Use create_before_destroy lifecycle on the environment resources to force the replacement

resource "octopusdeploy_environment" "env" {
  name     = "Env 1"
  space_id = octopusdeploy_space.space.id
  lifecycle {
    create_before_destroy = true
  }
}