Add additional eng/common check to `VerifyChangeLog` to prevent accidental version skip

For context.

Example. We had a service accidentally "skip" a minor version in it's history:


`4.5.0` -> `4.5.1` -> `4.6.0b1` -> `4.6.1`

As you can see, we skipped `4.6.0`. As the real release order should be

`4.5.0` -> `4.5.1` -> `4.6.0b1` -> `4.6.0` -> `4.6.1b1` -> `4.6.1`

Can we update the verify-changelog script to actually verify that we are always "leading" a new GA minor with a new Preview minor of the same minor and patch version.