!!![TASK] Remove old rendering

[jaapio]

This PR will remove the older sphinx rendering from this action.

Do not merge before the deadline to migrate to the new rendering

[linawolf]

Setting this to draft so it does not accidently get rendered

[fe-hicking]

If I read this right this is missing the mandatory settings.cfg>guides.xml conversion step?

And we probably need to add some other migrations to alter Includes.txt dynamically? And some others that are "most common issues"?

[jaapio]

Question is... Should we automate that? It might be better to just break as we might break the docs?

[linawolf]

We promised to make an on-the-fly migration

[garvinhicking]

From my experience, while the guides.xml automigration works quite flawless, usually there's always at least 1 or 2 directives that do not work out (shortcuts in Includes.txt, image inclusion). So probably the auto migration will never create a document that renders without errors (thus - will never get deployed).

But if there's a chance that 10 or 15% would work with an automigraiton, we should do that, it's better than 0% and letting them all fail.

[linawolf]

These directives usually cause warnings not errors. So it would get rendered but a few links or directives would not work. So it would get rendered but not Flawlessly as if you had done a manual migration and ensured there are no warnings

[jaapio]

Ok, I will re-add the step to detect the guides.xml and create one if it doesn't exist using the migration command.