Refactoring news-routes to be simpler and not using setInterval

[fcaps]

This is related to #454

1. there was no reason to go the complicated way and render news in the browser
2. there was no reason to use the setInterval in getNews.js router.get(/news/${page}) -> replaced with router.get(/news/:slug)
3. updated the news-slug to be actual url safe, but to not break any public links there is a fallback + redirect
4. started to use routers app.use("/news", newsRouter) to the express.js is not cluttered with code

Since the setInterval was adding so many routes to express, this has a good chance to be memory-leaking piece of code

[Sheikah45]

Just a quick note on your first point that we have to make sure the newshub still works with the client. As the news is just the rendering of the news page.

From the code I suspect you mean the individual articles but wanted to make sure.

[fcaps]

did not touch the http://localhost:8020/newshub, so changes will not affect it.
beware: the direct.faforever.xyz is not working correctly, so newshub will also not work if you test on faforever.xyz.

xyz will not have the newshub_externalLinkUrl in the items, see:

https://direct.faforever.com/wp-json/wp/v2/posts/?per_page=10&_embed&_fields=_links.author,_links.wp:featuredmedia,_embedded,title,newshub_externalLinkUrl,newshub_sortIndex,content.rendered,date,categories&categories=283

vs
https://direct.faforever.xyz/wp-json/wp/v2/posts/?per_page=10&_embed&_fields=_links.author,_links.wp:featuredmedia,_embedded,title,newshub_externalLinkUrl,newshub_sortIndex,content.rendered,date,categories&categories=283

[Brutus5000]

I don't really follow all changes, but we'll see on test