GA-138: new role names added for testing GA

[prashanthkumarnb]

JIRA link (if applicable)

https://tools.hmcts.net/jira/browse/GA-138

Change description

Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[ *] No

[hmcts-jenkins-a-to-c]

Plan Result

⚠️ Resource Deletion will happen ⚠️

This plan contains resource delete operation. Please check the plan result very carefully!

Plan: 1 to add, 0 to change, 2 to destroy.

• Delete
  • module.role-assignment-database-v15.null_resource.set-schema-ownership["role_assignment"]
• Replace
  • module.role-assignment-database-v15.null_resource.set-user-permissions-additionaldbs["role_assignment"]

Change Result (Click me)

  # module.role-assignment-database-v15.null_resource.set-schema-ownership["role_assignment"] will be destroyed
  # (because key ["role_assignment"] is not in for_each map)
  - resource "null_resource" "set-schema-ownership" {
      - id       = "501792913051080933" -> null
      - triggers = {
          - "force_trigger" = "2"
          - "name"          = "am-role-assignment-service-postgres-db-v15"
          - "script_hash"   = "ab1645969422eb52f19784fd29e26fd044ec09acb082bf6000c500468232933e"
        } -> null
    }

  # module.role-assignment-database-v15.null_resource.set-user-permissions-additionaldbs["role_assignment"] must be replaced
-/+ resource "null_resource" "set-user-permissions-additionaldbs" {
      ~ id       = "4920173339842491308" -> (known after apply)
      ~ triggers = { # forces replacement
          ~ "force_trigger"  = "2" -> "1"
            # (3 unchanged elements hidden)
        }
    }

Plan: 1 to add, 0 to change, 2 to destroy.