Core Rule Set: random passwords pass on the remaining password fields (closes #288)

Each app's sign-in, sign-up, password change and reset fields that had no
exclusion now skip the 35 rules random passwords set off, on that app's
paths and only when the query has no field of that name. Added gitea,
Vaultwarden's admin token, WordPress pass1/pass2/post_password and its REST
password, Drupal's forms and JSON, MediaWiki retype and password on the
pages that take them, Mastodon's challenge, and Nextcloud's confirm, reset,
change, share, LDAP renewal, encryption and OCS fields. Vaultwarden's
clients send a hash, which needs no exclusion.

Model: opus-5-5

internal/coreruleset/wordpress.conf

@@ -139,8 +139,8 @@ SecRule REQUEST_FILENAME "@streq /wp-login.php" \
 # The other passwords, which skip the same rules:
 #   pass1, pass2: resetting the password at /wp-login.php, changing it on the
 #   profile page and the page that edits a user, and adding a user; a
-#   multisite install also changes it on network/user-edit.php and
-#   user/profile.php
+#   multisite install also changes it under /wp-admin/network/ and
+#   /wp-admin/user/
 #   post_password: the password of a protected post, sent to /wp-login.php
 SecRule REQUEST_FILENAME "@rx ^/(?:wp-login\.php|wp-admin/(?:profile|user-edit|user-new|network/user-edit|user/profile)\.php)$" \
     "id:900715,phase:1,pass,nolog,chain"