feature request: allow for token rpc use wallet's pubkeys

[dimxy]

Feature request:
Currently any cc module rpc uses -pubkey param to access user's cc utxos. This limits development of various scripting tools which need to transfer tokens from multiple accounts in the wallet.
Suggestion is when tokens are transferred to use all available wallet's private keys. So, instead of one pubkey set by the -pubkey tokeld parameter, token rpcs should list all available pubkeys in the wallet and try to add token inputs for each of them.
This change will affect all tokenv2xxx rpcs (including assets cc rpcs).
However, for the tokenv2create rpc -pubkey param will still be used (to have the token creator determined)

[NutellaLicka]

This sounds great. The functionality should act as normal coins do. I'd suggest it would be a cool feature if you could allocate a specific pubkey to signing via the tokenv2create. Maybe this will create a hassle, but the functionality might be something along the lines of 'create the token to the pubkey provided (primary), or the pubkey set in the daemon if one is set(secondary)'.

The request was from a user that was trying to generate a pubkey for each user to deposit tokens into, but wasn't able to consolidate all of those tokens into a single address without having to relaunch the daemon with each new pubkey set.

[dimxy]

This could be arranged. I'd suggest if we create an alternate param set as a json. So we could use either the old-style params:
tokenv2createtokel token-name amount description 'json-with-tokel-data'
or a new wholly json param in which all creation params are passed:
tokenv2createtokel '{"name":"xxx", "pubkey":"pk", "amount":0.001, "TokelData": {"url":"myurl"} }'

[dimxy]

I suggest that we still require the -pubkey to be set and use it for the token change (although any pubkey in the wallet could be used for adding token inputs). Is this okay for apps like the bot?
(another option is to send token change to the same pubkey in the wallet that owned this tokenid)

[NutellaLicka]

What does the -pubkey option give us?

This will just mean any change will go to the pubkey address, but what does it mean for tokens?

I don't see if being a problem as long as they can send tokens from and to different pubkeys that aren't listed in the -pubkey option.

[dimxy]

The reason for -pubkey option usage in cc modules was that the native wallet.dat application does not know anything about cc transactions. So a cc rpc does not know which cc utxos belong to the user of a wallet and the user needs to tell to a cc rpc which cc utxos he would like to spend. Currently just '-pubkey' param is used for that (the second use case, yes, is sending the change to self)