minor #20994 Add missing upgrade path for Request::isMethodSafe() deprecation (chalasr)

This PR was merged into the 3.2 branch.

Discussion
----------

Add missing upgrade path for Request::isMethodSafe() deprecation

| Q             | A
| ------------- | ---
| Branch?       | 3.2
| Fixed tickets| #20990

Commits
-------

570a76c Add missing upgrade path for Request::isMethodSafe() deprecation

UPGRADE-3.2.md

@@ -94,6 +94,11 @@ HttpFoundation
      - `isInvalid`/`isSuccessful`/`isRedirection`/`isClientError`/`isServerError`
      - `isOk`/`isForbidden`/`isNotFound`/`isRedirect`/`isEmpty`
 
+  * Checking only for cacheable HTTP methods with `Request::isMethodSafe()` is deprecated 
+    since version 3.2 and will throw an exception in 4.0. Disable checking only for 
+    cacheable methods by calling the method with `false` as first argument or use 
+    `Request::isMethodCacheable()` instead.
+
 HttpKernel
 ----------
 

UPGRADE-4.0.md

@@ -151,6 +151,9 @@ HttpFoundation
     - `isInvalid`/`isSuccessful`/`isRedirection`/`isClientError`/`isServerError`
     - `isOk`/`isForbidden`/`isNotFound`/`isRedirect`/`isEmpty`
 
+ * The ability to check only for cacheable HTTP methods using `Request::isMethodSafe()` is
+   not supported anymore, use `Request::isMethodCacheable()` instead.
+
 HttpKernel
 ----------