Create upgrade guide for Plone 6.2 backend.

[mauritsvanrees]

For technical review, I tag @davisagli @gforcada @petschki.

I have fixed most Vale feedback, except these, which I don't know how to write better:

venv/bin/vale --no-wrap  docs/backend/upgrading/version-specific-migration/upgrade-to-62.md

 docs/backend/upgrading/version-specific-migration/upgrade-to-62.md
 33:11  suggestion  'is deprecated' looks like passive voice.    Microsoft.Passive         
 33:44  suggestion  'be removed' looks like passive voice.       Microsoft.Passive         
 62:29  warning     Avoid using acronyms in a title or heading.  Microsoft.HeadingAcronyms 

That last one is for "Classic UI" in the last header, I think.

---

📚 Documentation preview 📚: https://plone6--2002.org.readthedocs.build/

Specifically this page: /backend/upgrading/version-specific-migration/upgrade-to-62.

[stevepiercy]

You can ignore Vale warnings and suggestions, but errors should get a look. As part of my routine maintenance, I try to address the errors and reduce them. There's a long way to go yet, so the only thing I really care about for now is to not introduce new errors. Often it turns out to be a candidate for a new term in the glossary, and sometimes it's just some bad MyST markup.

I'll do a thorough editorial review in the next day or so, after the smart people do a technical review. Thanks for the PR!

[gforcada]

Nice write up!

[petschki]

thanks @mauritsvanrees ... currently there is nothing more to say for the template movements. Progress is tracked here plone/Products.CMFPlone#3953

[stevepiercy]

Minor tweaks, and a question and suggestion for reference to Python docs. I'm not sure if I got it right. Thanks for your work on this. It's really good!

[davisagli]

Aside from the pending suggestion, this looks good to me.

[mauritsvanrees]

I have rebased on 6.0 and force pushed, because the merge and revert of the multilingual PR which added the same file, gave a conflict.

[petschki]

I've created a TinyMCE license key config documentation here #2012

we should mention here, that TinyMCE got updated to v8 and that you're able to provide commercial tinymce license keys now.

[stevepiercy]

I've created a TinyMCE license key config documentation here #2012

we should mention here, that TinyMCE got updated to v8 and that you're able to provide commercial tinymce license keys now.

@petschki would you please amend your PR to do just that? It'd be better to keep the docs for a given feature together in the same PR.