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

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

* Add check for `phone-context`.

Add a check to PhoneNumberUtil that the value of the `phone-context` parameter of the tel URI follows the correct syntax as defined in [RFC3966](https://www.rfc-editor.org/rfc/rfc3966#section-3).

* Add check for `phone-context`.

Add a check to PhoneNumberUtil that the value of the `phone-context` parameter of the tel URI follows the correct syntax as defined in [RFC3966](https://www.rfc-editor.org/rfc/rfc3966#section-3).

* Add check for `phone-context`.

Add a check to PhoneNumberUtil that the value of the `phone-context` parameter of the tel URI follows the correct syntax as defined in [RFC3966](https://www.rfc-editor.org/rfc/rfc3966#section-3).

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

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

PiperOrigin-RevId: 509849832

* Add m2m sim number falsehood

* Add m2m sim number falsehood; correct text

Co-authored-by: penmetsaa <penmetsaa@google.com>

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

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

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

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

This commit resolves an issue with duplicate generation of metadata.h.

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

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

* Add BUILD_TOOLS_ONLY option

* Overide abseil install rules for subprojects

* Find and add abseil even when BUILD_GEOCODER=OFF

* Treat boolean variables as conditions

* Expose BUILD_SHARED_LIBS as a user configurable option

* Add BUILD_TESTING option

* Wrap test dependencies and targets in if (BUILD_TESTING)

* Refactor library build procedure to respect user defined configurations

* Export cmake package config files so downstream projects can use the library without creating a FindLibPhonenumber

* Bump version number to 8.13.0

Co-authored-by: penmetsaa <penmetsaa@google.com>

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

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

Co-authored-by:  <amergey@gmail.com>
Co-authored-by: Tijana Vislavski Gradina <tijanavg@google.com>

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

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

* Demo enhancements

* Update Demo portal

* Cleaning up auto generated, not very relevant archetype contents

* pom.xml ordering

* Cleanuping up unwanted changes

* Cleanuping up unwanted changes

* Update README

* Demo enhancements

* Updates after migration to Soy

Co-authored-by: Aravind <penmetsaa@google.com>

* Update pom.xml

* Update pom.xml

Co-authored-by: Tijana Vislavski Gradina <tijanavg@google.com>

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

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

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

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

This reverts commit 400bc9cf1d.

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

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

Remove unused leading_zero_possible field from phonemetadata.proto

Deleted all methods that refer to this.
Regenerated jars - because we no longer write a boolean for the removed proto field, all the java metadata files needed regenerating too.

Co-authored-by: Tijana Vislavski Gradina <tijanavg@google.com>

Previously, building the demo (ant -f javascript/build.xml compile-demo) would fail because the latest build.xml is incompatible with the version of closure-compiler we recommend here. With this change, the build will work again.

Co-authored-by: Tijana Vislavski Gradina <tijanavg@google.com>