add a name or label option to `litcli accounts`

[AndySchroder]

Is your feature request related to a problem? Please describe.

Way too much work to keep track of custodial accounts.

Describe the solution you'd like
add a name or label option to litcli accounts

Describe alternatives you've considered

Manually keep track of the id returned when you run litcli accounts create 50000.

[levmi]

Appreciate the feedback again! This one should be relatively straightforward and easy. We'll start to get this into our queue.

[AndySchroder]

I'm assuming it was implied here, but litcli accounts create, litcli accounts update, and litcli accounts remove should all accept the label that was assigned when creating instead of requiring the id to be used (both id or label should be usable).

[AndySchroder]

Another thing that would be very useful: If there is a way to make a GRPC call by the user of the macaroon to find out the name of the account that they are using. For example, say a macaroon is used by some machine to machine interfaces like I described in #583, the machine might want to be able to identify the name of the account that it is using so that it can remind the users (of the service that it is enabling) what account they need to refill if its allocated balance starts to get low (and maybe it can tell them on a monitoring screen built into that machine). This takes the burden off the users to keep track of what account is used where and it is one less piece of information to need to configure on the device. For example, say the machine is used in an organization (family, business, club, etc.) and it provides some critical service to the group, there are going to be various people that may be responsible for making sure everything is always running. They might have the ability to send more funds to each machine's account, but they don't have any control of the machines themselves. This feature would also allow you to rename the account and then that new name propagate out to all the devices or wallets that use the account.

Implementing this may be tricky because the RPC Middleware Interceptor doesn't really provide new grpc calls to LND, it just limits existing ones, so you may need to add some new message type to LND for metadata that can be intercepted to make it work.