Async javascript take 2

[joemasilotti]

A second take on #26 where the two public functions reply(to:) and reply(with:) are wrapped in a Task {} block. This lets a developer use the async version or non-async version depending on their preference. For example:

// From an async, throwing function:
func doSomething() async throws {
    reply(to: "connect") // Calls async, throwing version.
}

// From a non-async, non-throwing function:
func doSomethingNow() {
    reply(to: "connect") // Calls non-async version.
}

// From a non-async, non-throwing function (again):
func doSomethingLater() {
    Task { try await reply(to: "connect") } // Calls async, throwing version.
}

Notes

• The tests are currently failing. I think we had some tests that threw errors before that are now being exposed but I haven't dug in, yet.
• The actual change to the public API is in the most recent commit, 2a9aa0.

[svara]

This looks great @joemasilotti!
I like that we offer both standard and async versions.
I've left some feedback in #30.

[joemasilotti]

This is ready for re-review @svara!

[svara]

Nice work @joemasilotti!
I've noticed we were missing two non async reply(to...) functions. I added them in #31.
By adopting async/await we've made some of the classes not thread safe. I'll fix this in an upcoming PR today.

[joemasilotti]

@jayohms, does Android need an equivalent for this?

If not, I'll merge this then #24 and cut a new release!

[jayohms]

@jayohms, does Android need an equivalent for this?

Nope, no relevant concerns on the Android side. Go ahead and merge 👍

[svara]

@joemasilotti Let's wait with the merge. I've run into this issue https://forums.developer.apple.com/forums/thread/701553. I'll open a PR soon ~1h.