My own opinion is that:

• you’re then moving out of the area of testing your own company’s application & taking on the responsibility which Google should have with testing the captcha
• this introduces a further external concern to the testing & additional failure point 
• it introduces the need for additional tooling, resourcing, time and money to your project’s testing
• what are the requirements of this captcha from the business side? how critical is it & in what depth do they need it tested? have you had discussions with them
• Captcha can be hacked & bypassed now. It isn’t secure and is an annoyance to end users. Your team might want to consider its pros and cons before adopting in general

The general advice from boards like ISTQB is to bypass it & introduce a testing interface which won’t touch the captcha. I would agree with them here… captchas are more hassle than they are worth

Bypassing the Captcha is the best way

I think we can be able to test Captcha’s in many tools by using few Concepts.
In selenium it is developed, Test Complete tool has the ability to read captcha using OCR concept.

I hope, Tosca is also can read captcha using Vision AI concept. Just it will read the content from image Captcha and will be sending the same content to Text Box.