Allow querying a specified list of locks for a user

[arlai-mk]

Vote aggregators, such as Zephyrus, will likely manage a significant number of user locks within the Hydro platform. Currently, retrieving lock information requires using QueryMsg::AllUserLockups, which can be inefficient and time-consuming for aggregators with a large number of locks.

To improve performance and reduce query latency, it could be good to introduce a new query message: QueryMsg::SomeUserLockups (name can be different).

Suggested QueryMsg::SomeUserLockups parameters:

• address: The user's (or, in the above case, aggregator's smart contract) address.
• lock_ids: A vector containing the specific lock_ids for which we want to retrieve lock information.

[p-offtermatt]

Great idea!

[arlai-mk]

Quick question: would you see it as "erroring out" if we try to pass some lock_ids that do not belong to the user, or just silently skip them?

I was thinking of skipping them, but then I thought this could be the responsibility of the frontend / calling smart contract to make sure that only correct IDs are passed?

[p-offtermatt]

in general, I think it's easiest to skip. The caller will be able to tell which ones are missing by looking at the list of returns

[dusan-maksimovic]

Done through #216