Bug: Migrated Identity resolution

[UMR1352]

Description of change

• Fixes a bug in the resolution of a migrated Identity and introduces a new feature that populates the alsoKnownAs property of the resolved DID Document.
• Changed the type of the argument required to create a new Identity from raw bytes to IotaDocument.

Bug description

When resolving an Identity through its ObjectID foo a document with DID foo is resolved. If Identity foo is a migrated Identity from AliasOutput bar, DID bar will appear in the DID document's alsoKnownAs property.

When resolving a DID if foo is requested the resolver produces the same document obtaining by querying foo as an ObjectID but if DID bar is requested a DID Document with bar as DID and foo in alsoKnownAs is returned.

Schematically:

Identity { id: foo, legacy_id: bar } // Identity with ID foo that had been migrated from AliasOutput with ID bar

let identity_foo = client.get_identity(foo).await?;
assert_eq!(identity_foo.id(), foo);
assert!(identity_foo.also_known_as().contains(bar));

let did_doc = client.resolve_did(foo).await?;
assert_eq!(did_doc.id(), foo);
assert!(did_doc.also_known_as().contains(bar));

let did_doc = client.resolve_did(bar).await?;
assert_eq!(did_doc.id(), bar);
assert!(did_doc.also_known_as().contains(foo));

Type of change

• Bug fix (a non-breaking change which fixes an issue)
• Enhancement (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Fix