Core Rule Set: WordPress's names and addresses pass on more fields (closes #245)

Each field skips only the rules its recorded requests set off:

- page on all of wp-admin, and the JSON fields title, excerpt and name
  on /wp/v2/ routes: 930120, 932120, 932250 and 932260;
- p, postId and slug on all of wp-admin, and the JSON slug on /wp/v2/
  routes: 932120 and 932260, since WordPress writes these as slugs;
- url on the block editor's link previews and embeds, and a commenter's
  url: 930120 and 932120.

Every field keeps 932235. Add 61 requests recorded from WordPress 7.1.4
with these fields.

Model: opus-5-5

README.md

@@ -586,9 +586,9 @@ client's limits by tag. See "Request tags" in [`SPEC.md`](SPEC.md).
   HTTP and sign-in through Git Credential Manager on a code forge, and saving a
   post from the block editor on WordPress. On gitea's own paths, its searches,
   file names and branch names get through too. On WordPress's own paths, its
-  searches and file names do. On Drupal's own paths, the page to return to, its
-  searches and its names get through too. No setting undoes the changes; "Attack
-  detection" in [`SPEC.md`](SPEC.md) lists them.
+  searches, names and file names do. On Drupal's own paths, the page to return
+  to, its searches and its names get through too. No setting undoes the changes;
+  "Attack detection" in [`SPEC.md`](SPEC.md) lists them.
 - These apps work out of the box at the default settings, and their recorded
   ordinary requests pass the Core Rule Set:
     - gitea;