instead of silently succeeding, calendar-major should fail when the pom version is already '<today>.0.0'

[q3769]

If you have to release more than once on the same day today, you'd want the subsequent calendar major update to fail after the first of the day. The failure will force you to advance the semver. Silent success on multiple updates resulting in the same version appears to be a bad idea.