[Task] Add support for IOTA Names as the DID method-specific Identifier

## Description
Allow resolution of DID like `did:iota:acme` assuming the IOTA name `acme.iota`

## Motivation
Allow human-readable names for DID resolution and provide a way to link a Name to a domain.

## Resources
https://docs.iotanames.com/developer/integration

## To-do list
- [ ] Consider if target address is sufficient or we would want to enforce default address as well
- [ ] Consider hanling of `alsoKnownAs` field
- [ ] Extend IOTA DID specification

## Change checklist
Add an `x` to the boxes that are relevant to your changes, and delete any items that are not.

- [ ] The feature or fix is implemented in Rust and across all bindings whereas possible.
- [ ] The feature or fix has sufficient testing coverage
- [ ] All tests and examples build and run locally as expected
- [ ] Every piece of code has been document according to the documentation guidelines.
- [ ] If conceptual documentation (mdbook) and examples highlighting the feature exist, they are properly updated.
- [ ] If the feature is not currently documented, a documentation task Issue has been opened to address this.

Start with the IOTA Names integration resource and the repository’s existing DID method-resolution implementation. Determine how did:iota:acme maps to acme.iota, including the target/default address and alsoKnownAs decisions. Done means the feature is implemented in Rust and applicable bindings, with tests and relevant specification or documentation updates.

Written by the indexing model from the issue text.