* Configure Russian extension character доб as a valid one while parsing the numbers

* Escaping non ascii characters for better standardization.

* Added generated RU test data file. This is why travis test are failing at: https://travis-ci.org/googlei18n/libphonenumber/builds/407078226

* Removing manual support of encoded versions as it is already taken care in RegEx flags. Updated based on new review comments.

Source:
https://en.wikipedia.org/wiki/Mobile_telephone_numbering_in_India#6xxx_series

* Metadata updates for release 8.9.11

* Update to Release Notes as it was containg many other country codes

* Update Argentina geographic area codes

* Update Argentina Buenos Aires timezone

* Added Autonomous City of Buenos Aires prefix

* Update name of the cities - Remove new codes for 5411xxxx

* Addressed review suggestions

* Update comments in geocoding files

* Update comments in geocoding files

* Update formatForMobileDialling() to return E.164 format instead of national format for Uzbek phone numbers.

* Update java doc to be more clear

* Metadata updates for release 8.9.0

* release notes formatting fix

* Updated Mongolian carrier prefixes

Updated from Communications Regulatory Commission of Mongolian.
http://www.crc.gov.mn/k/4L/36

Another source: http://www.wtng.info/wtng-976-mn.html

* revert 97683|G-Mobile

The 2 operators changed have changed, Mobitel to Telekom Slovenije and Tušmobil to Telemach.

Uses the most recent S7 carrier data from Ofcom, with carrier names
being changed to friendlier versions (brand/trading names).

Data has also been compressed to reduce duplicate prefixes.

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

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

* Metadata updates for release 8.5.1

* Update release_notes.txt

* Metadata updates for release 8.5.0

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