Config Generation: Set a preferred field for resource names

[julienduchesne]

Part of #1745

SM and OnCall resources are covered in this PR. For these, the user configures a unique "name" but what is used as the resource ID is a unique database numerical ID

For the user's purposes, it's better to use the given "name" as the resource name. The numerical ID then remains internal, as it should

Example

This:

resource "grafana_synthetic_monitoring_check" "_12345" {
  job                = "testname"
  ...
}

Becomes

resource "grafana_synthetic_monitoring_check" "testname" {
  job                = "testname"
  ...
}

[github-actions]

In order to lower resource usage and have a faster runtime, PRs will not run Cloud tests automatically.
To do so, a Grafana Labs employee must trigger the cloud acceptance tests workflow manually.