swift: allow specifying text encoding at document creation

[miguelangel-dev]

Related pull-requests:

• Introduces text encoding: rust: allow specifying text encoding at document creation automerge#997

What is the goal?

Exposes new Automerge TextEncoding flag for creation of documents. It enables us to define the text representation to use in each of the operations without being forced to use Unicode Scalars in Swift.

blockers: pending to merge related PRs, and bump automerge core.

[heckj]

I've requested a few minor nits/changes in documentation wording for clarity, all as suggested changes. Additionally, I'd like to make sure that the exposed TextEncoding enum is documented through to the external Swift API that it's clear how those values related to Swift encodings.

The tests are the real gem of this PR - thank you - illustrating nicely how the text encoding changes effect cursor positions, etc.

What, exactly, is this holding on before we can/should merge this? Is there an upstream PR that's pending, or is that yet to be established?

[miguelangel-dev]

I've requested a few minor nits/changes in documentation wording for clarity, all as suggested changes. Additionally, I'd like to make sure that the exposed TextEncoding enum is documented through to the external Swift API so that it's clear how those values relate to Swift encodings.

Good call. Added Swift type and API documentation about TextEncoding in 71d4408

What, exactly, is this holding on before we can/should merge this? Is there an upstream PR that's pending, or is that yet to be established?

Exactly. This PR exposes changes done in upstream PR related to TextEncoding, and Cursor fixes. @alexjg is working on merging and releasing a new automerge version.

[miguelangel-dev]

@heckj requested your review because I changed the ci. Wasm job uses locally compiled libuniffi_automerge, but in mac, we were using the latest release precompiled Automerge. That change will align both and it opens to have two versions of the Automerge library: develop | release - in another way, in develop bindings won't be able to run ci using the latest Automerge library.

side note: PR is ready to merge.