GitLab

Keeps the non-obvious rationale (pod naming, repository injection, one-shot
promise settling, optional guards) and drops restatements of what the code
already shows.

Maps the JS config onto MyIdConfig.Builder, launches the SDK via
startActivityForResult and settles a single pending promise from the
activity-result callback.

handleActivityResult does not inspect the request code, so the listener filters
on its own code first to avoid settling the promise from an unrelated result.

MyID artifacts are not on Maven Central, and a consuming app re-resolves
transitive dependencies against its own repository set, so the repositories are
registered on all projects rather than only on this module. An opt-out property
is provided for apps that manage repositories centrally.

Repo becomes the myid-sdk npm package: library at root, RN 0.86.2 vanilla
example app in example/, Turbo Module codegen enabled, yarn 4 workspace.

The previous demo app targeted MyID SDK 2.x (clientId, withPassportData,
MyIdBuildMode), an API that no longer exists in 3.x, so it is removed rather
than migrated. Recoverable via the pre-rewrite tag.