chore: run pnpm run build before typedoc to avoid type errors

[yusefnapora]

I noticed earlier today that running pnpm run docs fails with a bunch of typescript errors unless you run pnpm run build first.

This just updates the docs npm script to pnpm run build && typedoc --out docs, so we'll always have build output to make typedoc happy.

error output if you don't build first

packages/access-client/src/agent.js:12:24 - error TS2307: Cannot find module '@web3-storage/capabilities/space' or its corresponding type declarations.

12 import * as Space from '@web3-storage/capabilities/space'
                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

packages/access-client/src/agent.js:13:26 - error TS2307: Cannot find module '@web3-storage/capabilities/voucher' or its corresponding type declarations.

13 import * as Voucher from '@web3-storage/capabilities/voucher'
                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

packages/access-client/src/agent.js:260:65 - error TS2694: Namespace '"/home/yusef/work/repos/w3protocol/packages/access-client/src/types"' has no exported member 'Top'.

260     const del = /** @type {Ucanto.Delegation<[import('./types').Top]>} */ (
                                                                    ~~~

packages/access-client/src/agent.js:286:7 - error TS2322: Type '{ identity: Client.URI<"mailto:">; }' is not assignable to type 'undefined'.

286       nb: { identity: URI.from(`mailto:${email}`) },
          ~~

many more lines omitted...

[yusefnapora]

BTW, I noticed that the reusable docs deploy workflow says that it's never been run, but looking at the CI config, it should get triggered whenever we release something that included a change to the capabilities or client packages.

I'm not sure if that's not working, or if we just haven't done any releases for those packages yet since setting up the CI workflows, but it may be worth double checking on the next release that those dependent workflows are getting run.

[gobengo]

@yusefnapora When I recently created the @web3-storage/capabilities subpackage, I also noticed that the 'release' workflow didn't seem to run the 'docs' job.

(aside: I am beginning to think it should be considered an anti-pattern to chain much logic in gh actions off of a release-please job. anecdotally, it seems to lead to quite fragile workflows with little recourse if e.g. release-please isn't working due to rate limits etc)