mmv1: migrate existing writeOnly fields to non-legacy version

[BBBmau]

Fixes hashicorp/terraform-provider-google#25965

This PR does the following:

1. introduces PropertyPath, the issue with write-only was the use of type.Lineage() which represents the Terraform path and not the MM path, this becomes important when dealing with fields inside a NestedObject marked as flatten_object: true
2. separation of constraint logic into it's own method - this refactors was to separate the constraints logic out of the buildWriteOnlyField
3. performs the migration of write_only_legacy -> write_only - this was trivial to do with the only extra logic needed was to resolve the flatten_object: true issue with payload within secret_version resource

Release Note Template for Downstream PRs (will be copied)

See Write release notes for guidance.

`mmv1`: migrate existing `writeOnly` fields to non-legacy version

[modular-magician]

Hi there, I'm the Modular magician. I've detected the following information about your changes for commit b9b7357:

Diff report

Your PR generated the following diffs in downstream repositories:

Repository	Diff Link	Changes
google provider	View Diff	11 files changed, 77 insertions(+), 84 deletions(-)
google-beta provider	View Diff	11 files changed, 77 insertions(+), 84 deletions(-)
terraform-google-conversion	View Diff	8 files changed, 10 insertions(+), 121 deletions(-)

Breaking Change(s) Detected

The following breaking change(s) were detected within your pull request.

• Field http_check.auth_info.password_wo within resource google_monitoring_uptime_check_config was added to exactly one of - reference
• Field http_check.auth_info.password within resource google_monitoring_uptime_check_config was added to exactly one of - reference
• Field secret_data_wo_version changed from TypeInt to TypeString on google_secret_manager_secret_version - reference
• Field secret_data_wo_version default value changed from 0 to <nil> on google_secret_manager_secret_version - reference
• Field sensitive_params.secret_access_key_wo_version changed from TypeInt to TypeString on google_bigquery_data_transfer_config - reference
• Field sensitive_params.secret_access_key_wo within resource google_bigquery_data_transfer_config was added to exactly one of - reference
• Field sensitive_params.secret_access_key within resource google_bigquery_data_transfer_config was added to exactly one of - reference

If you believe this detection to be incorrect please raise the concern with your reviewer.
If you intend to make this change you will need to wait for a major release window.
An override-breaking-change label can be added to allow merging.

Missing test report

Your PR includes resource fields which are not covered by any test.

Resource: google_bigquery_data_transfer_config (12 total tests)
Please add an acceptance test which includes these fields. The test should include the following:

resource "google_bigquery_data_transfer_config" "primary" {
  sensitive_params {
    secret_access_key            = # value needed
    secret_access_key_wo         = # value needed
    secret_access_key_wo_version = # value needed
  }
}

Test report

Analytics

Total Tests	Passed	Skipped	Affected
197	183	11	3

Affected Service Packages

• alloydb
• bigquerydatatransfer
• monitoring
• secretmanager

Learn how VCR tests work

---

Step 1: Replaying Mode

Action taken

Found 3 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit.

Click here to see the affected tests

• TestAccDatasourceSecretManagerSecretVersion_basic
• TestAccMonitoringUptimeCheckConfig_update_wo
• TestAccMonitoringUptimeCheckConfig_uptimeCheckConfigHttpPasswordWoExample

View the replaying VCR build log

---

Step 2: Recording Mode

Recording Mode	Replaying Rerun	Test Name
✅ Log	✅	TestAccDatasourceSecretManagerSecretVersion_basic
✅ Log	✅	TestAccMonitoringUptimeCheckConfig_update_wo
✅ Log	✅	TestAccMonitoringUptimeCheckConfig_uptimeCheckConfigHttpPasswordWoExample

🟢 All tests passed!

View the recording VCR build log or the debug logs folder for detailed results.

@BBBmau, @melinath VCR tests complete for b9b7357!