Remove CHANGELOG.md

[ctubbsii]

Remove the CHANGELOG file because it is a pain to manually edit, is easy to be incorrect, and does not add value beyond the value inherent in the source control repository (git log).

[hazendaz]

I think Renovate was reading from there. Or at least appeared to be doing so. See hazendaz/base-parent#669. But I think the change log in general was probably in wrong order where latest should be at top not bottom and depending if it was really reading there or something else since it noted it differently than you have the latest release posted. Most repos I've worked though don't have a change log like that especially smaller ones like this. And either some combination of marking it under github releases or milestones are used. Most often I find myself going right to the releases section anyways on projects to read in more detail and if that isn't used i typically just compare versions and look at history if its needed.

[hazendaz]

This is how renovate was showing...

Release Notes
revelc/formatter-maven-plugin
[v2.23.0](https://togithub.com/revelc/formatter-maven-plugin/blob/HEAD/CHANGELOG.md#ver-2230)

==========

    Support Eclipse 2023-03 (4.27, JDT 3.33) - requires jdk 11

[hazendaz]

so guess that answers that. it was looking into the changelog.

[hazendaz]

But I don't see much of a loss there. It didn't exactly make that jump out. Most PRs from Renovate do. That one was hidden in a section that had to be opened to see and besides it links back to the repo as well and typically our only reason for release is almost always just new eclipse versions. If anything, I'd use the Release section and tag the release with anything of note there in similar way. I think that can also be automated to pull milestones and do automatigically but I've not done that myself. I think spotbugs repo works that way.

[hazendaz]

See #844 as its very hard to understand and we need something.