Warnings about truncated bit array segments when building for javascript target

```
warning: Truncated bit array segment
┌─ /home/liv/source/gleam/gleeps/gleeps_shared/build/packages/youid/src/youid/uuid.gleam:246:64
│
246 │ let assert <> =
│ ^^^^^^^^

This segment is a 62-bit long int, but on the JavaScript target numbers
have at most 52 bits. It would be truncated to its first 52 bits.

Hint: Did you mean to use the `bytes` segment option?

warning: Truncated bit array segment
┌─ /home/liv/source/gleam/gleeps/gleeps_shared/build/packages/youid/src/youid/uuid.gleam:280:26
│
280 │ let assert <> = crypto.hash(crypto.Sha1, data)
│ ^^^^^^^^^

This segment is a 128-bit long int, but on the JavaScript target numbers
have at most 52 bits. It would be truncated to its first 52 bits.

Hint: Did you mean to use the `bytes` segment option?

warning: Truncated bit array segment
┌─ /home/liv/source/gleam/gleeps/gleeps_shared/build/packages/youid/src/youid/uuid.gleam:299:30
│
299 │ let assert <> =
│ ^^^^^^^^

This segment is a 62-bit long int, but on the JavaScript target numbers
have at most 52 bits. It would be truncated to its first 52 bits.

Hint: Did you mean to use the `bytes` segment option?

warning: Truncated bit array segment
┌─ /home/liv/source/gleam/gleeps/gleeps_shared/build/packages/youid/src/youid/uuid.gleam:357:18
│
357 │ let assert <> = <>
│ ^^

This segment is a 60-bit long int, but on the JavaScript target numbers
have at most 52 bits. It would be truncated to its first 52 bits.

Hint: Did you mean to use the `bytes` segment option?
```

Start by reproducing a JavaScript-target build and inspect the bit-array segments in src/youid/uuid.gleam at lines 246, 280, 299, and 357. Check how these segments behave on the JavaScript target; done means the build no longer emits the reported truncation warnings without breaking the UUID operations.

Written by the indexing model from the issue text.