Revert the update on {{URLPattern}} to [=URL pattern=]

I changed like so by mistake.  In this context, we would want to say
that it is not relevant to create a URLPattern object as a JSON input.
We need to say that because unlike JavaScript API, JSON API cannot take
a URLPattern object itself, which has URLPatternOptions.

spec.bs

@@ -2032,7 +2032,7 @@ If a specification has an Infra value (e.g., after using [=parse a JSON string t
 
 </div>
 
-Specifications may wish to leave room in their formats to accept options for {{URLPatternOptions}}, override the base URL, or similar, since it is not possible to construct a [=URL pattern=] directly in this case, unlike in a JavaScript API. For example, <cite>Speculation Rules</cite> accepts a "`relative_to`" key which can be used to switch to using the [=document base URL=] instead of the JSON resource's URL. [[SPECULATION-RULES]]
+Specifications may wish to leave room in their formats to accept options for {{URLPatternOptions}}, override the base URL, or similar, since it is not possible to construct a {{URLPattern}} object directly in this case, unlike in a JavaScript API. For example, <cite>Speculation Rules</cite> accepts a "`relative_to`" key which can be used to switch to using the [=document base URL=] instead of the JSON resource's URL. [[SPECULATION-RULES]]
 
 <h2 id=acknowledgments class=no-num>Acknowledgments</h2>