[css-navigation-1] Drop match-pattern/params/url from :link-to() and restructure.

This change:
* drops the match-pattern/match-params/match-url from :link-to(),
  leaving the match-params behavior as the only option,
* moves the at/with/to/from relation from inside the match-*
  function to before the route, and
* drops the navigation-* prefix from the at/with/to/from relation.

This is in preparation for a future change which will split :link-to()
into :link-to() and :active-navigation().

Author: dbaron

css-navigation-1/Overview.bs

@@ -431,9 +431,8 @@ by matching the relevant parts of the navigation URL to the link URL.
   /* match URLs like /en/movie/123 which is the English page
      about a movie with ID 123.  Be careful to specify the
      language part with a "*" but the ID part with a named
-     :id parameter so that matching using the 'match-params'
-     keyword (the default) will require equal IDs but allow
-     differences of language. */
+     :id parameter so that matching will require equal IDs
+     but allow differences of language. */
   pattern: url-pattern("/*/movie/:id");
 }
 
@@ -447,7 +446,7 @@ by matching the relevant parts of the navigation URL to the link URL.
 
    This depends on the --movie-details-with-id route
    declaring the ID but not the language with a named
-   parameter, and the use of match-params(navigation-with).
+   parameter, and the use of the 'with' keyword.
 
    This means that both the of the link and the other URL of
    the current navigation match the URL pattern defined by
@@ -457,8 +456,7 @@ by matching the relevant parts of the navigation URL to the link URL.
    match, containing the language, can be different.)
    */
 .movie-container:has(
-    > .movie-title:link-to(--movie-details-with-id
-                             with match-params(navigation-with))) {
+    > .movie-title:link-to(with --movie-details-with-id)) {
 
   view-transition-name: movie-container;
 
@@ -479,14 +477,9 @@ and the pseudo-class matches any element where:
 * the target of link matches the <<link-condition>>, as defined below.
 
 <pre class="prod def" dfn-type="type" nohighlight>
-<dfn><<link-condition>></dfn> = <<link-condition-base>> [ with <<navigation-match>> ]?
+<dfn><<link-condition>></dfn> = [ <<navigation-relation>> ]? <<link-condition-base>>
 <dfn><<link-condition-base>></dfn> = <<navigation-location>>
-  // Note: <<navigation-match>> is defining three functions
-  // with identical syntax.
-<dfn><<navigation-match>></dfn> = <<pattern-match-type>>( <<navigation-match-target>> )
-<dfn><<pattern-match-type>></dfn> = match-pattern | match-params | match-url
-<dfn><<navigation-match-target>></dfn> = navigation-at | navigation-with |
-                            navigation-from | navigation-to
+<dfn><<navigation-relation>></dfn> = at | with | from | to
 </pre>
 
 ISSUE: Should we use ''navigation-''(''at''/''with''/''from''/''to'') or
@@ -526,49 +519,36 @@ if the following steps return true:
 
     NOTE: This doesn't really matter because
     in this case the <<link-condition-base>> also doesn't match.
-1. Let <var>matchType</var> be the <<pattern-match-type>> of the
-    <<navigation-match>>.
-1. Let <var>matchTarget</var> be the <<navigation-match-target>> argument
+1. Let <var>matchRelation</var> be the <<navigation-relation>> argument
     of the <<navigation-match>>.
 1. Let <var>navigationURL</var> be:
-    : If <var>matchTarget</var> is ''navigation-at'',
+    : If <var>matchRelation</var> is ''at'',
     :: the document's [[=Document/URL=]].
-    : Otherwise, if <var>matchTarget</var> is ''navigation-with'',
+    : Otherwise, if <var>matchRelation</var> is ''with'',
     :: the <a>current other URL</a> of the document.
-    : Otherwise, if <var>matchTarget</var> is ''navigation-from'',
+    : Otherwise, if <var>matchRelation</var> is ''from'',
     :: the <a>current from URL</a> of the document.
-    : Otherwise (Assert: <var>matchTarget</var> is ''navigation-to''),
+    : Otherwise (Assert: <var>matchRelation</var> is ''to''),
     :: the <a>current to URL</a> of the document.
 1. If <var>navigationURL</var> is null, return false.
-1. : If <var>matchType</var> is ''match-pattern''
-    :: Return true if
-        the result of [=URL pattern/match|match a URL pattern=] given
-        <var>urlPattern</var> and <var>navigationURL</var> is not null;
-        otherwise return false.
+1. Let <var>navigationMatchResult</var> be the result of
+     [=URL pattern/match|match a URL pattern=] given
+     <var>navigationURL</var> and <var>urlPattern</var>.
 
-    : If <var>matchType</var> is ''match-params''
-    :: 1. Let <var>navigationMatchResult</var> be the result of
-            [=URL pattern/match|match a URL pattern=] given
-            <var>navigationURL</var> and <var>urlPattern</var>.
+1. If <var>navigationMatchResult</var> is null, return false.
 
-        1. If either <var>navigationMatchResult</var> is null, return false.
+1. For each property <var>prop</var> of {{URLPatternResult}} that is a
+    {{URLPatternComponentResult}}:
 
-        1. For each property <var>prop</var> of {{URLPatternResult}} that is a
-            {{URLPatternComponentResult}}:
+    1. If {{URLPatternComponentResult/groups}} of <var>prop</var> of
+        <var>targetMatchResult</var> is not equal to
+        {{URLPatternComponentResult/groups}} of <var>prop</var> of
+        <var>navigationMatchResult</var>,
+        then return false.
 
-            1. If {{URLPatternComponentResult/groups}} of <var>prop</var> of
-                <var>targetMatchResult</var> is not equal to
-                {{URLPatternComponentResult/groups}} of <var>prop</var> of
-                <var>navigationMatchResult</var>,
-                then return false.
+        ISSUE: Need to formally define equality of ordered maps.
 
-                ISSUE: Need to formally define equality of ordered maps.
-
-        1. Return true.
-
-    : If <var>matchType</var> is ''match-url''
-    :: Return true if <var>linkTarget</var> equals <var>navigationURL</var>;
-        otherwise return false.
+1. Return true.
 
 NOTE: Some of the design discussion for this feature has been in
 <a href="https://github.com/w3c/csswg-drafts/issues/13163">w3c/csswg-drafts#13163</a>.