Build coverage regex can't be removed from the plan

Created by: hulquest

Hello! I have been controlling GitLab Project definitions without issue. We are using provider version 3.16.1. Our administrators updated to 15.0.4-ee and the provider started to complain about a deprecated configuration variable build_coverage_regex. By complain, I mean the provider thinks it needs to alter the infrastructure even though this variable is no longer valid for Projects.

I realize this attribute was deprecated as a Project setting and moved to a configurable for the pipeline definition file. However, there is something wrong with the TF state and/or provider that doesn't recognize this variable as something to be ignored.

I removed the build_coverage_regex from the Project definition but Plan still detects that a change needs to be made to the current state even though the configuration option has been deprecated.

For instance:

  # gitlab_project.project["omniverse-cloud-ui"] will be updated in-place
  ~ resource "gitlab_project" "project" {
        id                                               = "63113"
      - issues_template                                  = "All files[^|]*\\|[^|]*\\s+([\\d\\.]+)" -> null
        name                                             = "Omniverse Cloud UI"
        tags                                             = []
        # (60 unchanged attributes hidden)

        # (2 unchanged blocks hidden)
    }

  # gitlab_project.project["omniverse-ui"] will be updated in-place
  ~ resource "gitlab_project" "project" {
      - build_coverage_regex                             = "All files[^|]*\\|[^|]*\\s+([\\d\\.]+)" -> null
        id                                               = "43897"
        name                                             = "Omniverse UI"
        tags                                             = []
        # (60 unchanged attributes hidden)

        # (2 unchanged blocks hidden)
    }

The provider does not realize the build_coverage_regex is deprecated and is associating the field with issue_template.

I expect the state to be updated with the 15.0.4 metadata in a way that doesn't cause the provider to recognize the two attributes as being out of compliance with the plan.