Updated docs for 9.0.0 release

Author: ezimuel

docs/release-notes/breaking-changes.md

@@ -18,7 +18,7 @@ Breaking changes can impact your Elastic applications, potentially disrupting no
 
 ## 9.0.0 [elasticsearch-php-client-900-breaking-changes]
 
-_No breaking changes_
+- **Use of PHP 8.1+:** Starting from 9.0.0 the `elasticsearch-php` client requires PHP 8.1+.
 
 % ::::{dropdown} Title of breaking change
 % Description of the breaking change.

docs/release-notes/deprecations.md

@@ -18,7 +18,7 @@ Review the deprecated functionality for Elasticsearch PHP Client. While deprecat
 
 ## 9.0.0 [elasticsearch-php-client-900-deprecations]
 
-_No deprecations_
+- **Utility::urlencode():** this function has been deprecated in favor of [rawurlencode()](https://www.php.net/manual/en/function.rawurlencode.php) of PHP (see [#1278](https://github.com/elastic/elasticsearch-php/issues/1278)).
 
 % Description of the deprecation and steps to update implementation.
 % For more information, check [PR #](PR link).

docs/release-notes/index.md

@@ -28,6 +28,8 @@ To check for security updates, go to [Security announcements for the Elastic sta
 - **Serverless client merged in:** the `elastic/elasticsearch-serverless` client is being deprecated, and its functionality has been merged back into this client. This should have zero impact on the way the client works by default. If an endpoint is available in serverless, the PHP function will contains a `@group serverless` phpdoc attribute.
 If you try to use an endpoint that is not available in serverless you will get a `410` HTTP error with a message as follows:
 "this endpoint exists but is not available when running in serverless mode".
+The 9.0.0 client can recognize that it is communicating with a serverless instance if you are using a URL managed by Elastic (e.g. `*.elastic.cloud`).
+If you are using a proxy, the client will be able to recognize that the host is serverless from the first response. Alternatively, you can explicitly indicate that the host is serverless using the `Client::setServerless(true)` function (`false` by default).
 - **New transport library with PSR-18 cURL client as default:** we've removed the Guzzle dependency from the client. By default, the built-in cURL-based HTTP client will be used if no other PSR-18 compatible clients are detected. See release [9.0.0](https://github.com/elastic/elastic-transport-php/releases/tag/v9.0.0) of elastic-transport-php.
 
 ### Fixes [elasticsearch-php-client-900-fixes]