Support subdomain matching in trial tokens

Support subdomain matching in trial tokens

This CL adds support for subdomain trial tokens, such that a properly
issued token will enable a trial for multiple subdomains, rather than a
single specified origin.

In bug 653349, it was proposed to use a leading "*" to indicate a
wildcard token (e.g. *.example.com). In this implementation, an explicit
flag was added to the token format. The explicit flag keeping the token
parsing simple, by keeping the url::Origin as the representation of the
origin, and avoiding custom string parsing.

BUG=653349
Review-Url: https://codereview.chromium.org/2411803002
Cr-Commit-Position: refs/heads/master@{#425168}
(cherry picked from commit 4f0cb8e9b16a270d0a7fd313f161b4c2c9a0df29)

Committed: https://chromium.googlesource.com/chromium/src/+/874cc8d1db06b6b7b04db41084f28a23956dbaf7

[chasej, 2016-10-18 21:51:58]

Description was changed from

==========
Support subdomain matching in trial tokens

This CL adds support for subdomain trial tokens, such that a properly
issued token will enable a trial for multiple subdomains, rather than a
single specified origin.

In bug 653349, it was proposed to use a leading "*" to indicate a
wildcard token (e.g. *.example.com). In this implementation, an explicit
flag was added to the token format. The explicit flag keeping the token
parsing simple, by keeping the url::Origin as the representation of the
origin, and avoiding custom string parsing.

BUG=653349

Review-Url: https://codereview.chromium.org/2411803002
Cr-Commit-Position: refs/heads/master@{#425168}
(cherry picked from commit 4f0cb8e9b16a270d0a7fd313f161b4c2c9a0df29)
==========

to

==========
Support subdomain matching in trial tokens

This CL adds support for subdomain trial tokens, such that a properly
issued token will enable a trial for multiple subdomains, rather than a
single specified origin.

In bug 653349, it was proposed to use a leading "*" to indicate a
wildcard token (e.g. *.example.com). In this implementation, an explicit
flag was added to the token format. The explicit flag keeping the token
parsing simple, by keeping the url::Origin as the representation of the
origin, and avoiding custom string parsing.

BUG=653349

Review-Url: https://codereview.chromium.org/2411803002
Cr-Commit-Position: refs/heads/master@{#425168}
(cherry picked from commit 4f0cb8e9b16a270d0a7fd313f161b4c2c9a0df29)

Committed:
https://chromium.googlesource.com/chromium/src/+/874cc8d1db06b6b7b04db41084f2...
==========

[chasej, 2016-10-18 21:51:59]

Committed patchset #1 (id:1) manually as
874cc8d1db06b6b7b04db41084f28a23956dbaf7.