implement is_human_call_lock

[robert-zaremba]

This is needed for Voting Body personhood checks.

[sczembor]

lets reuse the existing integration test for migration

[sczembor]

lgtm. I was thinking about potential shortcomings which may be a dapp setting the lock duration to some crazy long time (let's say a couple of yeas) either by a code bug or on purpose. Maybe there should be a way to release the lock before. The easiest way would be some admin method that can be called or a way for the dapp that the lock comes from to release it (it might be also good for some use cases where the i.e voting ends earlier than expected and the lock can be released).

Left few code suggestions in code mostly docs and comments. Also the integration test for migration is missing

[robert-zaremba]

I was thinking about potential shortcomings which may be a dapp setting the lock duration to some crazy long time (let's say a couple of yeas).

I will add a safety check to 2months.
However, we can't protect from a dapp proposing a user bad transactions. Examples:

• transfer of fungible tokens or NFTs to unwanted account
• soul transfer to some other account
• deleting account ...
  If user won't read tx, he will be screwed anyway.