Allow generate_name on cluster roles + bindings, and role bindings

[multani]

Description

Acceptance tests

• Have you added an acceptance test for the functionality being added?
• Have you run the acceptance tests on this branch?

Output from acceptance testing:

$ KUBE_CONFIG_PATH=~/.kube/config KUBE_CTX_CLUSTER=kind-kind make testacc TESTARGS="-run TestAcc.*Role.*_generatedName -count=1"
==> Checking that code complies with gofmt requirements...
go vet .
TF_ACC=1 go test "/home/jballet/projects/terraform/terraform-provider-kubernetes/kubernetes" -v -run TestAcc.*Role.*_generatedName -count=1 -timeout 3h
=== RUN   TestAccKubernetesClusterRoleBinding_generatedName
--- PASS: TestAccKubernetesClusterRoleBinding_generatedName (3.40s)
=== RUN   TestAccKubernetesClusterRole_generatedName
--- PASS: TestAccKubernetesClusterRole_generatedName (3.37s)
=== RUN   TestAccKubernetesRoleBinding_generatedName
--- PASS: TestAccKubernetesRoleBinding_generatedName (3.40s)
=== RUN   TestAccKubernetesRole_generatedName
--- PASS: TestAccKubernetesRole_generatedName (3.38s)
PASS
ok  	github.com/hashicorp/terraform-provider-kubernetes/kubernetes	13.586s

...

Release Note

Release note for CHANGELOG:

BUG FIXES:

* r/kubernetes_cluster_role: support `generate_name` to produce a unique random name
* r/kubernetes_cluster_role_binding: support `generate_name` to produce a unique random name
* r/kubernetes_cluster_role_binding_v1: support `generate_name` to produce a unique random name
* r/kubernetes_cluster_role_v1: support `generate_name` to produce a unique random name
* r/kubernetes_role_binding: support `generate_name` to produce a unique random name
* r/kubernetes_role_binding_v1: support `generate_name` to produce a unique random name

References

Fix #588

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[arybolovlev]

Hi @multani,

Thank you for your contribution! All looks great 👍🏻, just one small request from my end.

Could you please add a changelog file so we can then auto-generate a change log for the upcoming release?

It will be a simple text file in .changelog folder. Like this: .changelog/1899.txt. With the following content:

```release-note:enhancement
`resource/kubernetes_cluster_role`: add attribute `generate_name` to produce a unique random name
```

```release-note:enhancement
`resource/kubernetes_cluster_role_v1`: add attribute `generate_name` to produce a unique random name
```

```release-note:enhancement
`resource/kubernetes_cluster_role_binding`: add attribute `generate_name` to produce a unique random name
```

```release-note:enhancement
`resource/kubernetes_cluster_role_binding_v1`: add attribute `generate_name` to produce a unique random name
```

```release-note:enhancement
`resource/kubernetes_role_binding`: add attribute `generate_name` to produce a unique random name
```

```release-note:enhancement
`resource/kubernetes_role_binding_v1`: add attribute `generate_name` to produce a unique random name
```

Thank you! 🙏

[multani]

Hi @arybolovlev ,

I just added the changelog file now 🙇

[arybolovlev]

Amazing! 👍🏻 Thank you and congratulations on the first-time contribution! 🎉

Your changes will be available in the upcoming release. Please keep an eye on the release notes.

Happy New Year! 🎉

[multani]

Thanks for the merge @arybolovlev, this will be an excellent New Year's release! 🙇

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.