* [maven-release-plugin] prepare release v8.8.7

* [maven-release-plugin] prepare for next development iteration

* Update Javadoc for PhoneNumberUtil.PhoneNumberFormat enum about E.123 format.  We over.

* JS update

* Comment fix

* [maven-release-plugin] prepare release v8.8.6

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.8.5

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.8.3

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.8.2

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.8.0

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.7.1

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.6.0

* [maven-release-plugin] prepare for next development iteration

This hasn't been used for a long time.
Deleted all methods that refer to this, and removed the field from the test XML file (somehow this was missed) as well.
Regenerated jars - because we no longer write a boolean to indicate whether we have the possible number pattern or not all the java metadata files needed regenerating too.
Deleted some data from the js phone metadata implementation that isn't used by js as well (national number matcher pattern)

This enum won't be noticed by most users, because the country_code_source field of the phone number is only populated with ParseAndKeepRawInput, and in this case, this enum won't be used.

However, it provides a better result for users who incorrectly call parse() and then getCountryCodeSource() and expect to get a sensible answer; now they will get UNSPECIFIED instead of FROM_NUMBER_WITH_PLUS_SIGN which was the default before. In JS this method returns null, but getCountryCodeSourceOrDefault() will now return UNSPECIFIED instead.

The numeric values of the existing enums have not changed (relevant for JS and C++) and in Java the new enum was added to the end so that any stored serialized phone numbers should be able to be restored as they were before.

Suggested in issue #1218

Points people at parseAndKeepRawInput where appropriate.

*   It was confusing and unnecessary. Not every country that has short numbers beginning with a 0 had it, and it is not the only digit that could overlap with a national prefix and hence be interpreted incorrectly.

* [maven-release-plugin] prepare release v8.5.2

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.5.1

* [maven-release-plugin] prepare for next development iteration

* Metadata updates for release 8.5.1

* Update release_notes.txt

* [maven-release-plugin] prepare release v8.5.0

* [maven-release-plugin] prepare for next development iteration

* Metadata updates for release 8.5.0

* Corrected release notes as US geocding update is mentioned as new addition.

* Make canBeInternationallyDialled_API public in Java and CPP
* update notes in pending_code_changes.txt
* Remove TODO on canBeInternationallyDialled as it is already an public API in JS
* Make JS canBeInternationallyDialled API doc consistent with Java and CPP

* [maven-release-plugin] prepare release v8.4.3

* [maven-release-plugin] prepare for next development iteration

Alternate metadata and test metadata for C++ was regenerated not due to changes in this commit, but due to PR #1726 and that they should have been updated then.