move add and remove members to use wallet addresses

[insipx]

closes #357

• slight refactor to retry_async to allow retrying functions that accept a mutable ref
• remove add_members_by_installation_id and remove_members_by_installation_id
• wallet_address stored on intent instead of KeyPackages
• key packages are fetched while getting publish intents
• simple validation of Ethereum addresses in xmtp_cryptography (Does not cover EIP-55)

I accidentally pulled some changes from #354 from proto, so this should be merged after that (just some changes to GroupMembership names/tests that need to be merged in)

[neekolas]

I think something must have gotten miscommunicated in the goals here. We do need some mechanism to add members by installation_id. This is necessary to add new devices to a conversation, and to support revocation.

What we're hoping to achieve here is that when you are adding or removing a member by wallet address we look up the full list of installation_ids to add/remove at the last possible moment to ensure no changes slip in between the intent being created and being fulfilled.

[neekolas]

Looking through the discussion, including my own comments, I completely see how this confusion happened

[richardhuaaa]

Apologies for the confusion! I could probably have talked through the issue more in advance just to make sure we were all on the same page. Thanks for tackling this, and for always refactoring and improving the code quality!

[neekolas]

This looks great. Thank you @insipx