Check the presence of changelog for the latest stable release in History.md

[ia]

• Please check if the PR fulfills these requirements

• The changes have been tested locally
• There are no breaking changes

• What kind of change does this PR introduce?
  Detecting the presence of changelog for the latest stable release in History.md.

• What is the current behavior?
  We should add changelog manually but sometimes we may forget because there is no any test check for this.

• What is the new behavior (if this is a feature change)?
  Extend test step for docs using GitHub Actions with the following algorithm: check History.md for the latest stable release, check git tag for the latest stable release, and if they mismatch then trigger error.

• Other information:

Not sure how it will work at the moment of tagging though. I guess we will see. :)

But basically now the push of the new release tag to dev must be with the same commit of changelog to History.md. Otherwise there will be a reminder in the form of red build, but next commit of changes to History.md probably will fix it. That's the point after all.

Another one important notice for contributors, or what's new today I learned about git/hub: sometimes tags must be synced manually because for some reason just merging with upstream is not enough to sync some metadata such as tags, i.e.:

(in your local directory with the forked repo)
$ git fetch --tags upstream
$ git push --tags

Without this, Actions in forked repos may not be fetching the latest actual git tags from upstream even if anything else is properly merged, synced, and up-to-dated. 🤷‍♂️

[discip]

@ia
Although I understand roughly what this does, I not capable to approve your changes as I am not a programmer and therefore lack the necessary expertise. 😅
So you will have to wait for Ralim to approve it.