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

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

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

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

* Update link to isMobileNumberPortableRegion

Link was pointing to line 3275, but that function is now on line 3524.

* Make isMobileNumberPortableRegion a permalink

* Update FAQ.md

* Adding checking of leading digits before using an alternate format rule
when finding phone numbers in text (previously we thought this was done, hence why the data was there, but it wasn't).

Also some minor comment/formatting changes, and splitting a private helper method
into two.

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

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

* Add falsehood about accessibility of phone numbers

* Update wording for Falsehood

Updated "You can make a call to any phone number"

Grammer fixes, originally suggested in #2318

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

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

* Metadata updates for release 8.10.6

* Removed the region list that are only updated because of refactoring of RegEx.

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

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

For release 8.10.4

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

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

* followup to PR #2298 as sub version number is not mentioned earlier
* Increasing sub minor version to one more level based on new suggestions: https://github.com/googlei18n/libphonenumber/network/alert/java/demo/pom.xml/commons-fileupload:commons-fileupload/open

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

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

* Update version of dependency commons-fileupload
* More details to demo readme

The format of the data has changed such that formatting patterns now only refer to \d, not specific numbers, so we don't need the special handling in the AYTF code which converts them to \d.

* Defensive check added to FormatInOriginalFormat

Add a check that the FG is indeed in the national prefix before erasing it, in FormatInOriginalFormat. Matches java interpretation. It should always be there but if for some reason someone generates metadata with it not there we don't want to seg fault.

* Update phonenumberutil.cc

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

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

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

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

* Fixing brittle unit test of checking example short number

* Making same changes in CPP and Java

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

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

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

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

Updating AsYouTypeFormatter for better format selection for numbers dialled domestically

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

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

* Metadata updates for release 8.9.16

* Update release notes as there are many auto fixes to geocoding and other metadata files. Removing regions that do not have potential changes.

* Create 380.txt

* Update 380.txt

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

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

Starting in 2018, Mobile Vikings will also distribute new numbers with
prefix 456. Since Stievie is not a mobile brand, it can be ignored in
the listing.

As these mobile numbers are not yet distributed, there is no official
statement confirming this. The following FAQ page however already
mentions a 32456 number in Mobile Vikings context:
https://support.vikingco.com/hc/en-us/articles/360000313477-What-will-happen-after-activation-on-the-new-platform-