Differentiate what needs to be done for providing authoritative evidence (done over Issue Tracker) versus Pull Requests (done in GitHub).

This is for release 8.9.2

Due to migration from Github issues to Issue Tracker.

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

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

* Update new issue creation link to direct to Buganizer in demo portal

* Making issue tracker base url as contant value

Not all of the URls automatically redirect to https.  For example now https://libphonenumber.appspot.com goes to the https version.

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

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

See https://cloud.google.com/appengine/docs/standard/java/migrating-to-java8

* Metadata updates for release 8.9.0

* release notes formatting fix

* ShortNumberInfo metadata tooling - add missing fields to generated JSON.

Adjust javascript metadata generation tooling to include PhoneMetadata proto fields 29,30,31, and 33 that were previously excluded which are now needed for ShortNumberInfo.

* Add shortnumberinfo metadata to build metadata golden tests.

* Remove inaccurate comments in build tooling

* Add namespace to BuildMetadataJsonFromXml to support tool reuse

* Use updated build tooling to generate short number metadata file

* update phonemetadata.pb.js to match the current proto definition

* remove field 7 from phonemetadata.pb.js

* Update build tool to correctly namespacee the generated metadata files

* Stop field 32 from being populated as it is not used in the APIs

* remove metadata accessors for field 32.

* Add tests for connectsToEmergenyNumber and isEmergencyNumber.

Updated linter to include shortnumberinfo related files, and fixed some
lint issues existing with PhoneNumberUtil files.

* ShortNumberInfo functionality and tests ported. Unformatted and missing jsdoc

* Added comments, and fixed as many lint issues as possible.

* lint and comment review comments from andyst addressed.

* Add a golden metadata build test for short number metadata.

* Revert changes to the original phone metadata golden tests.

* Fix a lot of linting and jsdoc typing errors caught by the compiler.

* Add ShortNumberInfo to the javascript demo pages.

* Add ShortNumberIInfo porting to pending_code_changes.

* Add constants to golden tests.

* Update the build tooling

* uUdate pending changes to differentiate build and code changes

* Update build file, fix small test closure compilation issues

* Regenerate short number metadata to account for metadata updates between original generation and now.

* Move requires to alphabetical order

* 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

Fixes porting issue on macOS and maybe elsewhere.

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

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

This is for updating demo version in README.md for release 8.8.9

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

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

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

Make the demo link more obvious by putting it first, add note about the temporary transition to Issue Tracker, and mention Google Product Forums

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

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

* Add my name to metadata section

I contributed to update metadata of libphonenumber few times.

* Move Amir Farsi to right position

I moved my name in metadata section, to make the list sorted alphabetically.

Reordering of sections since many folks seem to skip the metadata / issue filing guidelines

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

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