Added missing planned_removal_date for google provider deprecations

[olegkachur-e]

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[SameerMesiah97]

Can you link the issue for this? Right now, the addition of the deprecation messages seems a bit scattershot. Is there a list of methods you are adjusting the warnings for or are you just going through the provider and adding this line to all warning messages that look like deprecation notifications?

[olegkachur-e]

Can you link the issue for this?

There is no active issue for this.
This change is a bit of the refactor clean-up.

There is a deprecation policy for the google provider: https://airflow.apache.org/docs/apache-airflow-providers-google/stable/deprecation-policy.html.

However there are some deprecation items, that impossible to cover with @deprecated or for the historical reasons does not have planned removal date.

So this change adds planned removal date for such items, respecting the 6 month notice rule.