use a name= instead of id=

back in 9d9aed39 (use <a id=""> instead of name, as name is not HTML5,
2023-06-01) we switched everything to id= but overlooked that id=
actually gets redacted by GitLab's sanitizer. With this, we should be
able to get the anchors through the filter even if it generates
non-conformant HTML5.

doc/accounts.md

@@ -21,7 +21,7 @@ policy](https://gitweb.torproject.org/community/policies.git/plain/membership.tx
 in case of discrepancy between the two documents, the membership
 policy overrules this document.
 
-## <a id="ldap-or-alias">Decision tree: LDAP account or email alias?</a> ##
+## <a name="ldap-or-alias">Decision tree: LDAP account or email alias?</a> ##
 
 Here is a simple decision tree to help you decide if a new contributor
 needs an LDAP account, or if an email alias will do. (All things being
@@ -69,7 +69,7 @@ If none of the above cases apply:
 
 See <a href="#aliases">Changing email aliases</a> for details.
 
-## <a id="new-account">New LDAP accounts</a> ##
+## <a name="new-account">New LDAP accounts</a> ##
 
 New accounts have to be sponsored by somebody who already has a torproject.org
 account.  If you need an account created, please find somebody in the project
@@ -135,7 +135,7 @@ and either approved or rejected.
 If the board indicates their assent, the sysadmin team will then create the
 account as requested.
 
-## <a id="retiring-account">Retiring accounts</a> ##
+## <a name="retiring-account">Retiring accounts</a> ##
 
 If you won't be using your LDAP account for a while, it's good security
 hygiene to have it disabled. Disabling an LDAP account is a simple
@@ -151,7 +151,7 @@ are sufficient to confirm a disable request."
 and accept that email forwarding for the person will stop working too,
 or add a new line in the email alias so email keeps working.)
 
-## <a id="get-access">Getting added to an existing group/Getting access to a specific host</a> ##
+## <a name="get-access">Getting added to an existing group/Getting access to a specific host</a> ##
 
 Almost all privileges in our infrastructure, such as account on a particular
 host, sudo access to a role account, or write permissions to a specific
@@ -183,14 +183,14 @@ Then you can run:
 
 See also: the `"Host specific passwords"` section below
 
-## <a id="aliases">Changing email aliases</a> ##
+## <a name="aliases">Changing email aliases</a> ##
 
 Create a ticket specifying the alias, the new address to add, and a
 brief motivation for the change.
 
 For specifics, see the "The sponsor will create a ticket" section above.
 
-### <a id="new-aliases">Adding a new email alias</a> ###
+### <a name="new-aliases">Adding a new email alias</a> ###
 
 #### Personal Email Aliases ####
 
@@ -204,13 +204,13 @@ Contributors.
 Tor Project Inc and Core Contributors can request group email aliases for new
 functions or projects.
 
-### <a id="existing-aliases">Getting added to an existing email alias</a> ###
+### <a name="existing-aliases">Getting added to an existing email alias</a> ###
 
 Similar to being added to an LDAP group, the right way to get added
 to an existing email alias is by getting somebody who is already on
 that alias to file a ticket asking for you to be added.
 
-## <a id="password-reset">Changing/Resetting your passwords</a> ##
+## <a name="password-reset">Changing/Resetting your passwords</a> ##
 
 ### LDAP ###
 
@@ -281,7 +281,7 @@ you don't need to nor can use sudo.)
 Do mind the delays in LDAP and sudo passwords change, mentioned in the
 previous section.
 
-## <a id="key-rollover">Changing/Updating your OpenPGP key</a> ##
+## <a name="key-rollover">Changing/Updating your OpenPGP key</a> ##
 
 If you are planning on migrating to a new OpenPGP key and you also want to
 change your key in LDAP, or if you just want to update the copy of your key

howto/backup.md

@@ -985,7 +985,7 @@ The GDB errors were documented in [issue 33732](https://gitlab.torproject.org/tp
 
 ## Disaster recovery
 
-<a id="Restoring-the-directory-server"></a>
+<a name="Restoring-the-directory-server"></a>
 
 Also known as "Restoring the directory server".
 

howto/git.md

@@ -240,7 +240,7 @@ Changes to most repositories are reported to:
 
  * Some repositories have a dedicated mailing list for commits at https://lists.torproject.org
 
-<a id="how-to-migrate-a-git-repository-from-legacy-to-gitlab"></a>
+<a name="how-to-migrate-a-git-repository-from-legacy-to-gitlab"></a>
 ## Migrating a repository to GitLab
 
 Moving a repository from Gitolite to GitLab proceeds in two parts. One

howto/gitlab.md

@@ -250,7 +250,7 @@ emoji to restrict your search, but be warned that some emojis have
 obvious. For example, `🎉`, `U+1F389 PARTY POPPER`, is found as
 `tada` in the list! See [this upstream issue for more details](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/29057).
 
-<a id="hooking-up-a-project-with-the-bots" />
+<a name="hooking-up-a-project-with-the-bots" />
 
 ## Publishing notifications on IRC
 

howto/postgresql.md

@@ -672,7 +672,7 @@ it isn't available in Debian.
 
 ## Direct backup recovery
 
-<a id="direct-restore-procedures" />
+<a name="direct-restore-procedures" />
 
 Note: this procedure **streams** the files from the backup server to
 the database server and restore directly. See the [disaster
@@ -1009,7 +1009,7 @@ The correct way to recover here is to issue a `pg_promote` statement:
 
 ## Indirect backup recovery
 
-<a id="indirect-restore-procedures" />
+<a name="indirect-restore-procedures" />
 
 Note: this procedure **copies** the backup files from the backup
 server to the database server and restores from those. It is a

policy/tpa-rfc-2-support.md

@@ -38,7 +38,7 @@ Which we translate in the following policy proposals:
 
 # Proposal
 
-<a id="how-to-get-help"></a>
+<a name="how-to-get-help"></a>
 
 <!-- if this section gets changed, also change support.md -->
 
@@ -239,7 +239,7 @@ admins][] (see below) to upgrade their services to keep
 up with the Debian release schedule.
 
 [service admins]: #service-admins
-<a id="service-admins"></a>
+<a name="service-admins"></a>
 
 ### Service admins