Dependabot and Renovate shows wrong changelog info

Many projects use dependabot to manage version updates of dependencies. It helps them to keep up to date with new versions, but also to understand what changed between versions. When a new version is available, a pull request with the related change is created. It's body (i.e. description) contains a changelog and list of commits between the different versions. For spotless-maven-plugin this does not work correctly, because it uses the changelog and commits of the root project.

For example https://github.com/camunda-cloud/zeebe/pull/8480 shows that it updates spotless-maven-plugin from 2.17.7 to 2.18.0, but the changelog shows the changes of the root project up to version `2.18.0`, instead of the changes of the maven-plugin. In addition, its shows the wrong changelog as source:
> Sourced from [spotless-maven-plugin's changelog](https://github.com/diffplug/spotless/blob/main/CHANGES.md)

Looking at the [dependabot issues about changelog](https://github.com/dependabot/dependabot-core/issues?q=is%3Aissue+is%3Aopen+changelog), this seems to be a common problem. However, it also looks like the dependabot team does not intend to change anything for it. So, I think spotless should improve its setup to correct dependabot's failure to deal with this, because it would help existing users of spotless, to learn about the changes in new versions.

Comienza examinando cómo spotless-maven-plugin publica su changelog y sus metadatos, especialmente CHANGES.md, y compáralo con el ejemplo de Dependabot en el pull request 8480. El trabajo estará terminado cuando los pull requests de actualización creados por Dependabot y Renovate muestren el changelog y los commits propios del plugin, así como la fuente correcta del changelog, en lugar de la información del proyecto raíz.

Escrito por el modelo de indexación a partir del texto del issue.