[Strapi 5] Breaking change for upgrade from apollo v3 to apollo v4

[MbonuJennifer]

In this PR:

Updated information on Apollo Server v3 upgraded to Apollo Server v4 in Strapi 5.

[strapi-cla]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ pwizla
❌ MbonuJennifer
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
documentation	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 19, 2024 5:26pm

[pwizla]

Please never write something is easy or difficult. This is left to the users' appreciation. See our 12 rules in the handbook.

Rewrite this with a different tone, something like: "For detailed instructions on how to migrate to Apollo v4, please refer to Apollo official docs (+ add external link here)."

[pwizla]

This section should only contain instructions and procedures.
Most of the sentences from the bullet points that you wrote describe differences, not what the user should actually do. Rewrite the sentences that the user knows what to do.

If you miss some information, please ask Ben Irvin, or if he's too busy at the moment, move these sentences to the Notes section and write something really generic in the Manual migration section, such as "To migrate to Strapi 5, users should manually update their code, taking into account all the items listed in the Notes section."

If you do this (i.e., do not actually describe what people can do), please also add a TODO comment in the Markdown file so we make sure we get back to it later and improve the manual migration section. Thank you!

[pwizla]

Thank you, Jennifer!
This breaking change item was not easy to handle.
The PR needs rework. I left several comments as a guidance. Hope that helps!