feat(wallet-service): added an api to find out if a wallet is using m…

[andreabadesso]

Motivation

The idea here is to allow the web-wallet to reject user requests to use the "single address" feature if the user wallet has more than one address being used

Acceptance Criteria

• We must have an API that returns whether a wallet has transactions in addresses other than the first one

Checklist

• If you are requesting a merge into master, confirm this code is production-ready and can be included in future releases as soon as it gets merged
• Make sure either the unit tests and/or the QA tests are capable of testing the new features
• Make sure you do not include new dependencies in the project unless strictly necessary and do not include dev-dependencies as production ones. More dependencies increase the possibility of one of them being hijacked and affecting us.

[tuliomir]

suggestion: The has-transactions endpoint name is misleading. I would expect it to return just if a wallet has been used at all, not if it is a single address wallet.

I would suggest something along the lines of:

• has-many-addresses or just wallet/addresses/has-many
• has-transactions-on-multiple-addresses
• is-single-address-wallet
• is-candidate-single-address-wallet
• has-transactions-outside-first-address