Configurable I2C Timeout

[raphaelhetzel]

Hi, similar to what has been described in #352, I have a sensor requiring a higher i2c delay.
I tried to follow the hints from the discussion and added a second constructor taking a delay value.
I did not try to use any semantic time values (second part of the discussion in the issue above) but instead just pass the raw timeout (similar to what esp-idf does).

Let me know if there are any required changes required or whether this change requires me to actually run all of the examples.

Must

• The code compiles without errors or warnings.
• All examples work.
• cargo fmt was run.
• Your changes were added to the CHANGELOG.md in the proper section.
• You updated existing examples or added examples (if applicable).
• Added examples are checked in CI

Nice to have

• You add a description of your work to this PR.
• You added proper docs for your newly added features and code.

[bjoernQ]

LGTM - Thank you!

[jessebraham]

Feels a bit strange to be mixing fugit types with primitive types within the same API, is there a particular reason u32 was chosen here instead of say DurationU32?

[bjoernQ]

The timeout is not expressed in time but in 2 ^ timeout clock cycles ... while it would be possible trying to do a lot of math to have a duration here it's probably not really worth it

[bjoernQ]

But maybe we should do it anyways - or document it at least

[raphaelhetzel]

The esp-idf also uses some non-time value here https://docs.espressif.com/projects/esp-idf/en/v4.3/esp32/api-reference/peripherals/i2c.html#_CPPv415i2c_set_timeout10i2c_port_ti . Not sure if anyone needs precise control over this or just "I need a higher timeout".