Add a `URLPatternList` primitive to efficiently match URLs against a collection of `URLPattern` objects.
URL routing use cases need to match an incoming URL against a potentially large number of patterns. Using an array of URLPattern objects that are checked sequentially is not efficient. An object representing a list of patterns can perform more efficient matching by using internal data structures that take advantage of commonalities between patterns in the list.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
No milestones specified