TypeScript signer is a library/SDK (#4105)

## Motivation

When building `linera-web` examples it sometimes happens that the
`package-lock.json` of `/signer` is incompatible/out of date. Both
signer and web client are used as SDK/libraries so should't have their
lock files committed.

`linera-web/build.bash` builds the client for the web but it didn't
prepare the TypeScript signers which required downstream client to
manually trigger that.

## Proposal

Signer and linera web client are a library/SDK and as such should not
have `package-lock.json` committed. This PR removes that file.

Add a line to `build.bash` that prepare signers (build javascript and
typescript files).

## Test Plan

Manually in `linera-web`.

## Release Plan

- Nothing to do / These changes follow the usual release cycle.

## Links


- [reviewer
checklist](https://github.com/linera-io/linera-protocol/blob/main/CONTRIBUTING.md#reviewer-checklist)

---------

Signed-off-by: deuszx <[email protected]>
Co-authored-by: James Kay <[email protected]>

Author: deuszx

.gitignore

@@ -26,3 +26,8 @@
 kubernetes/linera-validator/working/*
 node_modules
 **/dist/
+
+# Web client and signer are supposed to be used
+# as a library, so we don't want to
+# include their lock files.
+linera-web/**/*-lock.json

linera-web/build.bash

@@ -32,3 +32,5 @@ wasm-bindgen \
     --typescript \
     --target web \
     --split-linked-modules
+
+cd signer && pnpm prepare

linera-web/pnpm-lock.yaml

@@ -1,3 +1,3 @@
 packages:
-  - "signer"
   - "client"
+  - "signer"