Un-suspend apache-airflow-providers-apache-beam

### Under which category would you file this issue?

Providers

### Apache Airflow version

version 3

### What happened and how to reproduce it?

The beam provider has been [suspended](https://github.com/apache/airflow/pull/61926) a while ago, because of beam python sdk dependency for the grpcio constraint.

The constraint issue seems to be [resolved](https://github.com/apache/beam/pull/37633) and [released](https://github.com/apache/beam/milestone/40?closed=1) in a version of beam python sdk v.2.72.0.

### What you think should happen instead?

So provider can be brought back in a "regular" status, being released and maintained.

### Operating System

_No response_

### Deployment

None

### Apache Airflow Provider(s)

apache-beam

### Versions of Apache Airflow Providers

_No response_

### Official Helm Chart version

Not Applicable

### Kubernetes Version

_No response_

### Helm Chart configuration

_No response_

### Docker Image customizations

_No response_

### Anything else?

I need community guidance on how to "un-suspend" the provider?

Is it as straightforward as just reverting the https://github.com/apache/airflow/pull/61926?

I don't mind submitting a PR if needed.

### Are you willing to submit PR?

- [x] Yes I am willing to submit a PR!

### Code of Conduct

- [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)

Start by reading the suspension change in Apache Airflow pull request 61926 and the Apache Beam Python SDK resolution and v2.72.0 release references. Determine the project's required steps to restore apache-airflow-providers-apache-beam to regular status; done means the provider is unsuspended and can be released and maintained normally.

Written by the indexing model from the issue text.