"Version is higher than expected" warning may not be helpful

[nylen]

Feature Request

• Yes, I reviewed the contribution guidelines.

Describe your use case and the problem you are facing

When I need to fork a plugin for a specific site, I bump the version number to something like 99.0-upstream1.2.3. As far as I know, doing this any other way will require a bunch of other work and/or have other side effects like breaking translations.

Currently this triggers the warning described and implemented at #157, which is a false positive in this case.

Follow-up to #142.

Describe the solution you'd like

A way to disable this warning in a site's code. Arguably this might defeat the point of adding this alert, depending on how it is done.

However, I think any warning that WP-CLI can provide here is already pretty easy to defeat, and not very valuable compared to a more comprehensive approach like keeping the whole site inside a git repository and managing deploys more intelligently.

[nylen]

Note this also applies to other commands like wp theme update:

$ wp theme update --all
Warning: twentyfifteen: version higher than expected.
Warning: twentyseventeen: version higher than expected.
Warning: twentysixteen: version higher than expected.
Error: No themes updated.