First discovered in https://github.com/microsoft/vcpkg/pull/32595 , Google RE2 no longer provides their own custom StringPiece type, and instead use abseil::string_view (which may end up being std::string_view).

2d39b703d0 made StringPiece convertible to std::string and RE2 internally appears to have been changed over to use such conversions.

However, if we made the same change RE2 did internally, that would break compatibility with older versions of RE2.

There appear to be 2 ways  to fix this:
1. Both the old StringPiece and the new string_view have data() and size() members with which we can construct a new std::string without care for which one we got.
2. We can just copy the string_ member we already have.

This change does 2 but 1 would be reasonable if the authors wish for that resolution.

The issue links are dead since they point to the issues page for the GitHub page which is turned off.

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

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

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

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

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

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

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

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

---------

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

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

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

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

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

This reverts commit 5b4b3eb8e2.

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

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

* [StepSecurity] Apply security best practices

Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>

* Update codeql.yml

* Update codeql.yml

---------

Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
Co-authored-by: penmetsaa <penmetsaa@google.com>

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

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

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

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

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

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

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