Replace public_key_registry from cis3_sponsored_transaction with corresponding smart contract features

[DOBEN]

Purpose

addresses #258

After the new protocol update P6, smart contracts can now get the public_keys of accounts within the smart contract code. There is also a new check_account_signature function available.

The public_key_registry is not necessary anymore in the sponsored transaction smart contract and should be replaced.

Note: This PR is a draft and has some local dependencies hardcoded to simplify the use of a "local/unreleased" smart contract testing integration library. This needs to be updated/changed before merging.
https://github.com/Concordium/concordium-smart-contract-tools/tree/main/concordium-smart-contract-testing

Changes

• Remove public_key_registry.
• Add check_account_signature to verify the signature in the smart contract.
• Replace old publicKeyOf function (returned a tuple pair (public key, nonce)) with two separate functions publicKeyOf (returns public keys for a vector of accounts) and nonceOf (returns nonces for a vector of accounts).
• Add integration tests.
• Add integration testings for a signature transfer permit function call.
• Add integration testings for a signature update operator permit function call.
• Signature/PublicKey types were removed from concordium_std and are now available via concordium_contracts_common.

[abizjak]

I am still not sure what the best option for this is. Once we release the libraries we can use the published ones for this PR, but we should also try to think about a long-term solution.

[abizjak]

Suggested change

	let mut inner_key_map: BTreeMap<KeyIndex, VerifyKey> = BTreeMap::new();
	inner_key_map.insert(
	KeyIndex(0u8),
	VerifyKey::Ed25519VerifyKey(
	ed25519_dalek::PublicKey::from_bytes(&PUBLIC_KEY)
	.expect("Should be able to create public key"),
	),
	);
	let credential_public_keys = CredentialPublicKeys {
	keys: inner_key_map,
	threshold: SignatureThreshold::ONE,
	};
	let mut key_map: BTreeMap<CredentialIndex, CredentialPublicKeys> = BTreeMap::new();
	key_map.insert(
	CredentialIndex {
	index: 0u8,
	},
	credential_public_keys,
	);
	let keys = AccountAccessStructure {
	keys: key_map,
	threshold: AccountThreshold::ONE,
	};
	let rng = &mut rand::thread_rng();
	let keypairs = AccountKeys::singleton(rng);
	let keys: AccountAccessStructure = (&keypairs).into();

[abizjak]

If we unify AccountSignature and TransactionSignature this will become

let signature = keypairs.sign(&to_bytes(...))

[abizjak]

Suggested change

	let mut inner_key_map: BTreeMap<u8, PublicKey> = BTreeMap::new();
	inner_key_map.insert(0u8, PublicKey::Ed25519(concordium_std::PublicKeyEd25519(PUBLIC_KEY)));
	let credential_public_keys = concordium_std::CredentialPublicKeys {
	keys: inner_key_map,
	threshold: SignatureThreshold::ONE,
	};
	let mut key_map: BTreeMap<u8, concordium_std::CredentialPublicKeys> = BTreeMap::new();
	key_map.insert(0u8, credential_public_keys);
	let account_public_keys: AccountPublicKeys = AccountPublicKeys {
	keys: key_map,
	threshold: AccountThreshold::ONE,
	};
	let account_public_keys = (&keypairs).into();

[limemloh]

The first version only supported accounts with one key, and the reason I remember for this was to simplify the endpoints for registering keys. So now that we are removing those endpoints, I think we should support multi-sig accounts here

[DOBEN]

close as completed in
#363
#359