fix(android): the token field is named for what it is, not for one server

It said "gitea token", which is wrong for the other transport this client
speaks: the same field carries a Bearer token to the PHP endpoint. The URL
decides which - naming the field after one of them makes it false for the
other.

Worth stating plainly while here: this client does NOT do WebDAV. There is no
Basic auth in PMA.SyncClient and no username field; only the desktop still
speaks it. Supporting it here would need both.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

android-client/web/app.html

@@ -248,7 +248,11 @@
            de cet ecran, mais le seul qu'un regard par-dessus l'epaule
            attrapait. On le saisit une fois ; le relire n'a aucun usage. -->
       <div class="in-wrap">
-        <input class="field-in" id="tok" placeholder="gitea token (read + write)"
+        <!-- NEUTRE : c'est l'URL qui decide de la nature du jeton, pas ce
+             champ. Une adresse d'API Gitea en fait un jeton d'acces personnel
+             envoye en « token » ; l'endpoint PHP en fait un « Bearer ». Le
+             nommer d'apres un seul des deux le rend faux pour l'autre. -->
+        <input class="field-in" id="tok" placeholder="access token"
                type="password" autocomplete="off">
         <div class="in-x" data-clear="tok">&#215;</div>
       </div>