docs: clean up beta indicators

Author: gene-redpanda

README.md

@@ -1,9 +1,5 @@
 # Redpanda Terraform Provider
 
-![Beta Release](https://img.shields.io/badge/release-beta-red.svg)
-
-> **Warning**: This is a beta release. The API is subject to change.
-
 The Redpanda Terraform Provider is a [Terraform](https://www.terraform.io/) plugin that allows you to create and manage
 resources on [Redpanda Cloud](https://redpanda.com/redpanda-cloud).
 

docs/index.md

@@ -6,8 +6,6 @@ description: |-
 
 # Redpanda Provider
 
-[Beta Release](https://img.shields.io/badge/release-beta-red.svg)
-
 The Redpanda provider is designed for managing Redpanda clusters and Kafka resources in Redpanda Dedicated and Cloud environments. It supports the provisioning, management, and configuration of clusters and Kafka resources, facilitating seamless integration into Terraform workflows.
 
 <!-- schema generated by tfplugindocs -->

docs/resources/cluster.md

@@ -1309,20 +1309,12 @@ variable "replication_factor" {
 
 ## BYOVPC
 
-![Beta Release](https://img.shields.io/badge/release-beta-red.svg)
-
-This feature is in beta and is still under development or awaiting fixes. It can be used at some risk.
-
 This accepts a network and other elements created by the end user inside their cloud provider account (currently limited to AWS) and builds a Redpanda Cluster inside it.
 
 There is [a module](https://github.com/redpanda-data/terraform-aws-redpanda-byovpc) provided for convenience of the end user here that handles the necessary setup. It contains outputs for the inputs the provider requires.
 
 ### AWS BYOVPC
 
-![Beta Release](https://img.shields.io/badge/release-beta-red.svg)
-
-This feature is in beta and is still under development or awaiting fixes. It can be used at some risk.
-
 Has the same requirements as the AWS BYOC Cluster in addition to ARNs for numerous resources that the end user must create.
 
 ```terraform
@@ -1515,10 +1507,6 @@ variable "replication_factor" {
 
 ### GCP BYOVPC
 
-![Beta Release](https://img.shields.io/badge/release-beta-red.svg)
-
-This feature is in beta and is still under development or awaiting fixes. It can be used at some risk.
-
 Has the same requirements as the GCP BYOC Cluster along with the additional requirement for numerous resources that the end user must create.
 
 ```terraform

templates/index.md.tmpl

@@ -6,8 +6,6 @@ description: |-
 
 # Redpanda Provider
 
-[Beta Release](https://img.shields.io/badge/release-beta-red.svg)
-
 The Redpanda provider is designed for managing Redpanda clusters and Kafka resources in Redpanda Dedicated and Cloud environments. It supports the provisioning, management, and configuration of clusters and Kafka resources, facilitating seamless integration into Terraform workflows.
 
 {{ .SchemaMarkdown | trimspace }}

templates/resources/cluster.md.tmpl

@@ -57,30 +57,18 @@ The account [must have fairly wide ranging permissions](https://docs.redpanda.co
 
 ## BYOVPC
 
-![Beta Release](https://img.shields.io/badge/release-beta-red.svg)
-
-This feature is in beta and is still under development or awaiting fixes. It can be used at some risk.
-
 This accepts a network and other elements created by the end user inside their cloud provider account (currently limited to AWS) and builds a Redpanda Cluster inside it.
 
 There is [a module](https://github.com/redpanda-data/terraform-aws-redpanda-byovpc) provided for convenience of the end user here that handles the necessary setup. It contains outputs for the inputs the provider requires.
 
 ### AWS BYOVPC
 
-![Beta Release](https://img.shields.io/badge/release-beta-red.svg)
-
-This feature is in beta and is still under development or awaiting fixes. It can be used at some risk.
-
 Has the same requirements as the AWS BYOC Cluster in addition to ARNs for numerous resources that the end user must create.
 
 {{ tffile "examples/byovpc/aws/main.tf" }}
 
 ### GCP BYOVPC
 
-![Beta Release](https://img.shields.io/badge/release-beta-red.svg)
-
-This feature is in beta and is still under development or awaiting fixes. It can be used at some risk.
-
 Has the same requirements as the GCP BYOC Cluster along with the additional requirement for numerous resources that the end user must create.
 
 {{ tffile "examples/byovpc/gcp/main.tf" }}