Nimble: Use DispatchTimeInterval for interval configurations

[ikesyo]

It would provide more descriptive APIs and type safety.

// before
expect(...).toEventually(equal(...), timeout: 0.1)
waitUntil(timeout: 1) { done in ... }

// after
expect(...).toEventually(equal(...), timeout: .milliseconds(100))
waitUntil(timeout: .seconds(1)) { done in ... }

[ikesyo]

Closed by #718.

[NicholasTD07]

Long time user of the Quick and Nimble framework since Swift 1.0, I think. Really appreciate all the work you have been doing!

May I ask why this change happened? Without any description or context, it's hard to understand what's the benefit of this change. I have recently upgraded to Nimble, v9.0.0. I am pretty sure I am not the only one who got a lot of broken tests due to this change.

[ikesyo]

@NicholasTD07 Sorry for the inconvenience. I've just updated this issue's description.

[NicholasTD07]

@ikesyo Thanks! Yeah, it definitely help with type safety and also a clearer API.