docs: Remove Evolution product notifications and references

[Ibochkarev]

Description

Removes Evolution product notifications and remaining user-facing references from the MODX docs (en, ru, es where those pages exist).

Homepage sections that sent readers to Evolution / evo.im are gone. FAQ 1.1 now describes MODX 2.x and 3.x only. Upgrade TOCs no longer promote 1.x migration guides. Those URLs stay as short stubs so existing redirects keep working. Comparative asides and Extras blurbs that named Evolution are rephrased for modern MODX.

Path segments under upgrading/evolution/ remain for redirect stability. They no longer document or advertise Evolution CMS.

Affected versions

3.x docs branch. The same content lives on 2.x for many of these pages, so a follow-up cherry-pick or merge to 2.x may be needed.

Relevant issues

Fixes #30

[Mark-H]

Hmm, this might warrant some discussion. On one hand I agree that Evo is from so long ago that cleaning up some references to it is a good idea, but some of these changes seem like rewriting history. There's nothing wrong acknowledging something came from Evo or was inspired by something for Evo, as long as the focus is on the current product.

Thoughts? // @rthrash @jaygilmore

[jaygilmore]

@Mark-H in general, I don't mind the removal of many of the references of Evo, especially for 3.x. It doesn't add anything and the historical reference is insignificant. One could argue it actually adds to cognitive load referencing a project we haven't managed for nearly 15 years.

I am a but unsure it it's our place to remove Evo references from the documentation of third-party Extras. That said, upon review, much of it is extraneous and doesn't add anything of value to people and since Evo.im is no longer compatible with a lot of this stuff, it's entirely irrelevant to both parties.

Finally, I did note that Bob Ray's GoRevo's Evo references should not be removed or altered since it's entire purpose is to migrate Evo sites to Revo and we've used this tool in the last couple of years for customer legacy sites as an effective way to move from Evo to Revo.