Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [io.github.algorandecosystem:falcon-signatures-mobile-sdk](https://github.com/algorandecosystem/falcon-signatures-mobile) from 0.0.19 to 0.1.0.
- [Release notes](https://github.com/algorandecosystem/falcon-signatures-mobile/releases)
- [Commits](https://github.com/algorandecosystem/falcon-signatures-mobile/compare/v0.0.19...v0.1.0)

---
updated-dependencies:
- dependency-name: io.github.algorandecosystem:falcon-signatures-mobile-sdk
  dependency-version: 0.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

Signers (e.g. wallets) can mutate the transactions they are given, so the
transactions that were built aren't necessarily the ones that reach the
network. The group was sent successfully, but the results (and the
`pendingTransactionInformation` lookups behind `confirmations`) were derived
from the pre-mutation transactions, whose IDs were never on chain.

Resolve the transactions from the signed transactions in
`sendAtomicTransactionComposer`, `TransactionComposer.simulate()` and the
legacy `sendTransaction`, so `txIds`, `transactions`, `groupId` and
`confirmations` all reflect what was actually sent.

docs: fix transactions concepts link on asset page