Fix consistent return response from PubSubPullOperator

[MaksYermak]

In this PR #42080 the issue #41877 was fixed only for PubSubPullSensor. But because PubSubPullSensor and PubSubPullOperator both use the PubsubPullTrigger. This issue exists for PubSubPullOperator as well.

In the current PR I have applied the same solution for PubSubPullOperator.

---

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.

[VladaZakharova]

Hi @shahar1 !
This PR is a part of new upcoming change in google provider and i was hoping it will be released in the nearest release (5th May). Can you please take a look and maybe merge it, so we can try to aim till the release day? :)
thank you in advance!

[Lee-W]

I'm good with the change, but would like to have @shahar1 take another look :)