Update Rust crate async-lock to v3 (#310)

[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [async-lock](https://togithub.com/smol-rs/async-lock) | dependencies |
major | `2.7.0` -> `3.0.0` |

---

### Release Notes

<details>
<summary>smol-rs/async-lock (async-lock)</summary>

###
[`v3.0.0`](https://togithub.com/smol-rs/async-lock/blob/HEAD/CHANGELOG.md#Version-300)

[Compare
Source](https://togithub.com/smol-rs/async-lock/compare/v2.8.0...v3.0.0)

- **Breaking:** Add an enabled-by-default `std` feature that allows
using this crate without the standard library.
([#&#8203;43](https://togithub.com/smol-rs/async-lock/issues/43))
- Support blocking and non-blocking operations on the same locks.
([#&#8203;56](https://togithub.com/smol-rs/async-lock/issues/56))
- Switch to a more efficient event notification mechanism.
([#&#8203;43](https://togithub.com/smol-rs/async-lock/issues/43))

###
[`v2.8.0`](https://togithub.com/smol-rs/async-lock/blob/HEAD/CHANGELOG.md#Version-280)

[Compare
Source](https://togithub.com/smol-rs/async-lock/compare/v2.7.0...v2.8.0)

- Fix a bug where the `SemaphoreGuard::acquire_arc` future would busy
wait under certain conditions
([#&#8203;42](https://togithub.com/smol-rs/async-lock/issues/42)).
- Add a `Semaphore::add_permits()` function to increase the number of
available permits on the semaphore
([#&#8203;44](https://togithub.com/smol-rs/async-lock/issues/44)).
- Make `RwLockReadGuard` covariant over its lifetime
([#&#8203;45](https://togithub.com/smol-rs/async-lock/issues/45))
- Add `RwLockReadGuardArc`, `RwLockWriteGuardArc`, and other reference
counted guards for the `RwLock` type
([#&#8203;47](https://togithub.com/smol-rs/async-lock/issues/47)).
- Loosen the `Send`/`Sync` bounds on certain future types
([#&#8203;48](https://togithub.com/smol-rs/async-lock/issues/48)).
- Fix UB caused by the `MutexGuardArc::source` function allowing the
user to drop an object in a different thread than the one it was
acquired in
([#&#8203;50](https://togithub.com/smol-rs/async-lock/issues/50)). This
is a breaking change, but in the name of soundness. Therefore it doesn't
break any valid behavior.
- Fix a bug where this crate would not compile properly on `wasm64`
([#&#8203;51](https://togithub.com/smol-rs/async-lock/issues/51)).

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "every weekend" (UTC), Automerge - At
any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/bitwarden/sdk).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4zMS41IiwidXBkYXRlZEluVmVyIjoiMzcuMzEuNSIsInRhcmdldEJyYW5jaCI6Im1hc3RlciJ9-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

crates/bitwarden-uniffi/Cargo.toml

@@ -12,7 +12,7 @@ crate-type = ["lib", "staticlib", "cdylib"]
 bench = false
 
 [dependencies]
-async-lock = "2.7.0"
+async-lock = "3.0.0"
 chrono = { version = ">=0.4.26, <0.5", features = [
     "serde",
     "std",