Added mention of temporary Composer conflicts needed during v4 update (#2391)

* Added mention of temporary Composer conflicts needed during v4 update
* Apply suggestions from code review
* update_from_4.5.md: `conflict` to upgrade to 4.5.latest
The fixes appeared in 4.5.1 and 4.5.6 so you may still need them when coming from 4.5.0, right?
* update_from_4.4.md: `conflict` to upgrade to 4.5.latest
`conflict` entries are needed between 4.4.0 and 4.4.latest (4.4.4) but are not needed from 4.4.latest (4.4.4) to 4.5.latest (4.5.7)

---------

Co-authored-by: Adrien Dupuis <[email protected]>

Author: mnocon

docs/snippets/update/temporary_v4_conflicts.md

@@ -0,0 +1,10 @@
+!!! caution "Temporary need of Composer `conflict`"
+
+    To go through this update, [map the conflicting packages](https://getcomposer.org/doc/04-schema.md#conflict) in your `composer.json` file as following:
+    ```json
+    "conflict": {
+        "jms/serializer": ">=3.30.0",
+        "gedmo/doctrine-extensions": ">=3.12.0"
+    },
+    ```
+    These entries can be removed after fully upgrading to v4.6 LTS.

docs/update_and_migration/from_3.3/to_4.0.md

@@ -9,6 +9,8 @@ See [a list of all changed namespaces, configuration key, service names, and oth
 
 An additional compatibility layer makes the process of updating your code easier.
 
+[[% include 'snippets/update/temporary_v4_conflicts.md' %]]
+
 !!! note "Symfony 5.4"
 
     If you are using Symfony 5.3, you need to update your installation to Symfony 5.4.

docs/update_and_migration/from_4.0/to_4.1.md

@@ -4,6 +4,8 @@ This update procedure applies if you are using v4.0.0.
 
 Go through the following steps to update to v4.1.
 
+[[% include 'snippets/update/temporary_v4_conflicts.md' %]]
+
 !!! note
 
     During the update process you can encounter the following error:

docs/update_and_migration/from_4.1/update_from_4.1.md

@@ -6,6 +6,8 @@ description: Update your installation to the v4.2.latest version from an v4.1 ve
 
 This update procedure applies if you are using a v4.1 installation.
 
+[[% include 'snippets/update/temporary_v4_conflicts.md' %]]
+
 ## Update from v4.1.x to v4.1.latest
 
 Before you update to v4.2, you need to go through the following steps to update to the latest maintenance release of v4.1 (v[[= latest_tag_4_1 =]]).
@@ -143,4 +145,4 @@ otherwise you can encounter errors during compiling.
 ``` bash
 rm -Rf node_modules
 rm -Rf yarn.lock
-```
+```

docs/update_and_migration/from_4.2/update_from_4.2.md

@@ -6,6 +6,8 @@ description: Update your installation to the latest v4.3 version from v4.2.x.
 
 This update procedure applies if you are using a v4.2 installation.
 
+[[% include 'snippets/update/temporary_v4_conflicts.md' %]]
+
 ## Update from v4.2.x to v4.2.latest
 
 Before you update to v4.3, you need to go through the following steps to update to the latest maintenance release of v4.2 (v[[= latest_tag_4_2 =]]).

docs/update_and_migration/from_4.3/update_from_4.3_new_commerce.md

@@ -5,6 +5,8 @@ description: Update procedure to v4.4 for people who don't use Commerce packages
 
 This update procedure applies if you have a v4.3 installation, and you do not use Commerce packages.
 
+[[% include 'snippets/update/temporary_v4_conflicts.md' %]]
+
 ## Update from v4.3.x to v4.3.latest
 
 Before you update to v4.4, you need to go through the following steps to update to the latest maintenance release of v4.3 (v[[= latest_tag_4_3 =]]).

docs/update_and_migration/from_4.3/update_from_4.3_old_commerce.md

@@ -10,6 +10,8 @@ Note that all commerce packages as of v4.4 are deprecated and will be removed in
 Until that time, they will be maintained by [[= product_name_base =]] with fixes, including security fixes, but they won't be further developed.
 Old packages are replaced by [the all-new Ibexa Commerce packages](ibexa_dxp_v4.4.md#all-new-ibexa-commerce-packages).
 
+[[% include 'snippets/update/temporary_v4_conflicts.md' %]]
+
 ## Update from v4.3.x to v4.3.latest
 
 Before you update to v4.4, you need to go through the following steps to update to the latest maintenance release of v4.3 (v[[= latest_tag_4_3 =]]).
@@ -219,4 +221,4 @@ run data migration required by the Customer Portal applications feature:
 ```bash
 php bin/console ibexa:migrations:import vendor/ibexa/corporate-account/src/bundle/Resources/migrations/application_internal_fields.yaml --name=2022_11_07_22_46_application_internal_fields.yaml
 php bin/console ibexa:migrations:migrate --file=2022_11_07_22_46_application_internal_fields.yaml
-```
+```

docs/update_and_migration/from_4.4/update_from_4.4.md

@@ -12,6 +12,8 @@ Before you update to v4.5, you need to go through the following steps to update
 
 ### Update the application to v4.4.latest
 
+[[% include 'snippets/update/temporary_v4_conflicts.md' %]]
+
 Run:
 
 === "[[= product_name_content =]]"
@@ -30,6 +32,16 @@ Run:
     composer require ibexa/commerce:[[= latest_tag_4_4 =]] --with-all-dependencies --no-scripts
     ```
 
+!!! note "Remove temporary Composer `conflict`"
+
+    You can now remove the temporary Composer `conflict` entries from your `composer.json` file:
+    ```diff
+        "conflict": {
+    -        "jms/serializer": ">=3.30.0",
+    -        "gedmo/doctrine-extensions": ">=3.12.0"
+        },
+    ```
+
 ## Update from v4.4.latest to v4.5
 
 When you have the latest version of v4.4, you can update to v4.5.