Update iota.rs to include timeout bugfix

[PhilippGackstatter]

Description of change

Update iota.rs to the latest dev commit in order to include the timeout bugfix from iotaledger/iota.rs#848. Previously, the requet_timeout builder option was essentially ignored, and since this is the only option we expose, the fix is important to us.

This also comments out the currently unused identity-comm crate, because libjose's rsa = 0.5 dependency requires zeroize < 1.5, which is incompatible with the iota.rs requirement of (now) 1.5.3 of said crate. identity-comm is currently unused and will need a refactor anyway.

Type of change

Add an x to the boxes that are relevant to your changes.

• 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

How the change has been tested

Ran a local test (not added to the code base) to make sure the fix works for us:

#[tokio::test]
async fn test_timeout() {
  let client = ClientBuilder::new()
    .request_timeout(std::time::Duration::from_millis(1))
    .build()
    .await
    .unwrap();

  let error = client.publish_json("index", &[0u8; 32]).await.unwrap_err();

  assert!(matches!(error, crate::Error::ClientError(iota_client::Error::ReqwestError(_))));
}

Change checklist

Add an x to the boxes that are relevant to your changes.

• I have followed the contribution guidelines for this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[cycraig]

Broken in Wasm due to timing code added in iotaledger/iota.rs@47e5f66

[eike-hass]

Broken in Wasm due to timing code added in iotaledger/iota.rs@47e5f66

How did you catch this / how could we have caught that in CI?

[cycraig]

It was caught in CI https://github.com/iotaledger/identity.rs/runs/5541464592?check_suite_focus=true

[eike-hass]

It was caught in CI https://github.com/iotaledger/identity.rs/runs/5541464592?check_suite_focus=true

that is good to hear

[cycraig]

Looks good to me! Annoying to retain dead code but it will be addressed Soon™.