* [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-

* Update ShortNumberInfo test regarding example number change for region AM. Unlike PhoneNumberUtilTest, ShortNumberInfoTest uses real metadata for unit testing.

* Changing the region as Travis tests do not pass with old short metadata of AM

* Making same changes in CPP and JS

Demo version update in readme file for release 8.9.14

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

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

* Metadata updates for release 8.9.14

* Update region list in release_notes to the regions that contain only potential changes. Other are having only cleanup updates

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

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

* Cleanup in continuation to support to russian extension characters

* Nit: \xBE (uppercase E) for consistency

* Ensure the test runner decodes files as UTF-8

Before this change, the `document.charset` of the HTML test files would be 'windows-1252' when accessed through the `file://` protocol, resulting in issues with library or test files containing non-ASCII symbols.

This patch ensures tests still run correctly when files contain non-ASCII symbols.

* Ensure ASCII-safety of source code

Change troubleshooting CMake on mac Protobuf path to .dylib

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

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

Presently we are supporting unicode characters of Russian extension characters manually in JS.
This should be changed in future by setting right flags.
Previous PR: #2223

Surprisingly, we need not set unicode characters of upper case '\u0414\u041E\u0411'. This woks fine.