Release urbit-os-v2.135

…umber.

Resolves urbit#6377 - stuck %eth-watcher due to get-block-by-number zero-padded number RPC failure

Per suggestion at https://github.com/urbit/urbit/pull/6377/files/f5eeffef587b06bc93540536cf88a10e49dc77fd#r1128704330
Moves x-co:co into num-to-hex-minimal.

Fix stuck %eth-watcher due to get-block-by-number zero-padded number RPC failure.

This commit refactors `sur/hood.hoon` and changes the signature of the
`+vats` generator thus:

```hoon
|=  $:  [now=@da eny=@uvj bec=beak]
        $@(~ [?(%suspended %running %blocking %nonexistent) ~])
        $:  verb=?
            show-suspended=?
            show-running=?
            show-blocking=?
            show-nonexistent=?
        ==
    ==
```

Called with a single positional argument, `+vats` will show only those
desks fitting the description given, while keyword parameters allow
finer-grained control over which desks are described. The `verb`
parameter determines whether the full load of desk information be shown,
or a subset thereof.

Resolves urbit#6297.

We were retrying failed kelvin upgrades as many times as we had apps
that needed to be suspended, because suspending an app triggers an
attempt to run the next kelvin upgrade.  This suspends all those apps in
one batch move, and then tries the next kelvin upgrade only once at the
end.

Fixes urbit#6407

Partially addresses urbit#6285

hotfix clay rebuild loop

+vats options

sss: Unsubscribing and permissions

…-desk

arvo: add more files to |new-desk generator

Release urbit-os-v2.136

…-contact-scry

ames: add last-contact scry endpoint

Merge master back to develop after urbit-os-v2.136 release

Instead of including wrapped-task as-is in most call traces, we now only
include it in traces for crashing (harden task) calls. For everything
else, we include only the tag of the resulting $task.

Closes urbit#6444.

dill: exclude wrapped-task from most +call traces

ames: ping faster to sponsors

arvo: print module compilation times

behn: propagate errors in deferred moves

\urbit#1775

The JSON standard rejects all un-escaped, un-printable characters EXCEPT
for the delete character (ID 127, i.e. 0x7F).

See: https://www.crockford.com/mckeeman.html
Via: https://www.json.org/json-en.html

JSON supports Unicode as both UTF8 sequences and escaped UTF16. Unicode
points U+10000 to U+10FFFF are encoded as two consecutive escaped UTF16
units known as a surrogate pair. The JSON decoder was previously
treating surrogate pairs as two individual escaped UTF16 units. In
addition, the JSON standard allows hexadecimal letters to be either
uppercase or lowercase, which the parser was not respecting.

See:
- https://www.crockford.com/mckeeman.html
- https://www.json.org/json-en.html
- https://en.wikipedia.org/wiki/UTF-16#Code_points_from_U+010000_to_U+10FFFF

Git issue: urbit#1776

JSON supports Unicode as both UTF8 sequences and escaped UTF16. UTF8 is
encoded as between 2 and 4 bytes, the first byte of which governs the
length. The JSON parser was previously accepting any non-ASCII bytes as
UTF8 in any order.

See:
- https://www.crockford.com/mckeeman.html
- https://www.json.org/json-en.html
- https://en.wikipedia.org/wiki/UTF-8#Encoding

The backspace character was not being escaped like other invisible
characters.

Encode JSON to cord instead of tape. Code copied from @joemfb 's
version.