fix: look for the correct capability in client.capability.upload.get (

#1357)

I was seeing some strange errors in the nft.storage work I'm doing right
now and realized it's a result of a copypasta bug in `upload-client`
where we query for the wrong capability when putting together this
invocation.

We missed this in testing because tests use one big proof, which means
that asking for `upload/add` is equivalent to asking for `upload/get` -
in an ideal world I'd spend a bit of time untangling this but since I'm
at the bottom of a stack of shaved yaks I'd like to get this shipped and
file an issue to come back to this later.

package.json

@@ -17,7 +17,7 @@
     "docs:markdown": "pnpm run build && docusaurus generate-typedoc"
   },
   "devDependencies": {
-    "@arethetypeswrong/cli": "^0.12.2",
+    "@arethetypeswrong/cli": "^0.15.3",
     "@docusaurus/core": "^3.0.0",
     "@docusaurus/preset-classic": "^3.0.0",
     "docusaurus-plugin-typedoc": "^0.21.0",

packages/w3up-client/src/capability/upload.js

@@ -26,7 +26,7 @@ export class UploadClient extends Base {
    * @param {import('../types.js').RequestOptions} [options]
    */
   async get(root, options = {}) {
-    const conf = await this._invocationConfig([UploadCapabilities.add.can])
+    const conf = await this._invocationConfig([UploadCapabilities.get.can])
     options.connection = this._serviceConf.upload
     return Upload.get(conf, root, options)
   }