Add support of semantic minor change about binary-compatibility-validator

[qwwdfsad]

Hi,

It seems like what you are proposing is a higher level of abstraction than binary-compatibility-validator operates on. You can build such behaviour on top of BCV programmatic API, but BCV itself neither has the notion of semantic versioning nor it should have:

• apiCheck is not aware of any versions at all and neither has ways to detect the version for which it checks API for
• It's not clear who is responsible for updating apiDump in that case. What prevents you from adding a new API in minor version 1 and removing it in minor version 2 if the dump is not updated?
• Different libraries (e.g alpha or experimental) can treat semantic versioning pretty frivolously while still keeping track of binary compatibility