Add clients to updatecli automation

[lcawl]

Relates to #2308 (review)

Per https://docs-v3-preview.elastic.dev/elastic/docs-builder/tree/main/contribute/release-new-version "This action [updating the versions.yml file] can be performed by any member of the docs team. It's also automated for many products".

This PR copies the existing pattern for the clients, which all use releases like this:

• https://github.com/elastic/elasticsearch-java/releases
• https://github.com/elastic/elasticsearch-js/releases
• https://github.com/elastic/elasticsearch-net/releases
• https://github.com/elastic/elasticsearch-php/releases
• https://github.com/elastic/elasticsearch-py/releases
• https://github.com/elastic/elasticsearch-ruby/releases
• https://github.com/elastic/elasticsearch-rs/releases
• https://github.com/elastic/go-elasticsearch/releases

[theletterf]

+CC @v1v

[v1v]

LGTM, just a very tiny comment regarding the alphabetical order

[Mpdreamz]

Thank you for following up with this @lcawl ! 🙏

[theletterf]

@Mpdreamz I'm going to comment out the CF GCP blocks for now, since they're making updatecli fail — checked with @constanca-m about this. We can uncomment them back at the end of December.

[Mpdreamz]

Thanks for chasing that @theletterf !