Proposal: Remove changelogs

[johnbillion]

I propose that the "Changelog" section that's manually included at the bottom of most of the pages in the hosting handbook are removed. There are two problems with these changelogs:

1. The information is mostly of no value to the reader. Picking this page at random, the changelog is quite substantial in length but contains nothing that adds to the content already on the page. Everything in the changelog is meta information and not relevant to the reader.
2. The changelog can wrongly give the impression that content is out of date. For example the latest changelog entry on the security page was almost three years ago, but the page was in fact updated just a few weeks ago. Evergreen content doesn't always need to be continually updated. A visible changelog places too much emphasis on recency.

If there is a need to make note of an important change to a particular page then yes let's include that as an exception, but otherwise I think all the changelogs should be removed.

Any objections?

[javiercasares]

This was something the Documentation Team had and we copied that way. Also, it was before the theme update, and having GitHub as the changelog, I don't think it should be a problem to delete/update the documentation without it.

I'm offering myself to fix it if we decide to move on this way.