fix(clublog): use OpsLog's own application API key

The embedded key was registered to XV9Q, not to OpsLog. Not a cosmetic
detail: Club Log identifies the client software by that key, so every
OpsLog upload in the world was attributed to that callsign. Its owner
received the abuse warning OpsLog earned when the on-close sweep was still
posting hundreds of QSOs through the realtime endpoint - and a revocation
aimed at them would have cut Club Log uploads for every user of this
program at once.

G7VJR issued a key for "OpsLog" on request. Same mechanism, same UX: the
key identifies the software, the operator still supplies their own e-mail
and password, so it authorises nothing on its own.

Club Log asks that it not be published in source code. The source is on a
private remote and only the built exe is released, but it remains
recoverable from that binary by anyone who looks - as it is for every
logger that embeds one. It is an identifier that can be attributed, not a
secret.

changelog.json

@@ -2,8 +2,12 @@
   {
     "version": "0.26.0",
     "date": "",
-    "en": [],
-    "fr": []
+    "en": [
+      "Club Log uploads are now identified as OpsLog. They were credited to another station's application key, which took the blame for them."
+    ],
+    "fr": [
+      "Les envois Club Log s’identifient désormais comme OpsLog. Ils étaient attribués à la clé applicative d’une autre station, qui en portait la responsabilité."
+    ]
   },
   {
     "version": "0.25.9",