cli: Support dot-delimited petname paths

[rekmarks]

Following #2022, we should support dot-delimited petname paths in the CLI such that wherever a petname for an existing value is provided, a path can be provided instead. This path will then be passed to the mailbox lookup method, which will attempt to resolve the value.

For example, this should work:

$ endo eval '10' --name ten
10
$ endo eval 'foo' foo:INFO.ten.source
10

Note that the parsePetNamePath() utility should be used for dot-delimited path parsing in the CLI.

See also discussion in #1915.

TODO

• daemon: Add termination hook to lookup formula #2041
• eval feat(cli,daemon): Support dot-delimited petname paths for CLI eval command #2034
• cancel
  • Prior attempt: feat(cli,daemon): Support pet name paths in kill command #2043
• --as feat(cli): Support dot-delimited paths for --as option in all commands #2047
  • dismiss
  • inbox
  • list
  • reject
• make feat(daemon,cli): Make and store at path #2281
• store feat(daemon,cli): Make and store at path #2281
• adopt Further endo daemon CLI support for dot-delimited paths #2325
• bundle Additional dot-delimited petname path support #2296
• catAdditional dot-delimited petname path support #2296
• dismiss
• follow Additional dot-delimited petname path support #2296
• install Further endo daemon CLI support for dot-delimited paths #2325
• mkdir Further endo daemon CLI support for dot-delimited paths #2325
• mkguest
• mkhost
• move feat(cli,daemon): Add move CLI command #2227
• open Additional dot-delimited petname path support #2296
• reject
• remove Further endo daemon CLI support for dot-delimited paths #2325
• request Further endo daemon CLI support for dot-delimited paths #2325
• resolve
• run Additional dot-delimited petname path support #2296
• send
• show feat(cli): Expand options for storing values #2237
• spawn Further endo daemon CLI support for dot-delimited paths #2325

N/A

• clean
• help
• log
• purge
• restart
• start
• stop
• ping
• where

[kriskowal]

endo rename should be replaced with endo mv|move when we can support dot delimited paths, and we should support dot delimited paths for both the source and target. We should also guarantee that a move occurs in a single JavaScript event unless the dot-delimited path reaches outside the local dæmon. That will require the move operation to walk from formula to formula for both the source and target path before falling through to the lookup protocol. We will need a corresponding protocol for “depositing” a formula identifier to the target “directory” and allow that protocol to work remotely.

E(remoteDirectory).deposit(name, nonce, addresses). See ocapn/ocapn#105

The local behavior occurs if the nonce exists in the daemon and just writes the corresponding name and formula identifier to the local pet store (directory). Otherwise, the remote behavior is to create a “remote” formula that captures the nonce and addresses. So, if the remote restarts, it can reestablish a connection to the node that the nonce calls home.