Bump async-lock from 2.8.0 to 3.2.0

[dependabot]

Bumps async-lock from 2.8.0 to 3.2.0.

Release notes

Sourced from async-lock's releases.

v3.2.0

• Add missing methods for blocking on locking with types wrapped in Arc (#71).

v3.1.2

• Bump event-listener to version v4.0.0. (#69)

v3.1.1

• Add a note to the documentation comparing this crate against libstd's locks. (#58)

v3.1.0

• Add a Default implementation for OnceCell (#63).

v3.0.0

• Breaking: Add an enabled-by-default std feature that allows using this crate without the standard library. (#43)
• Support blocking and non-blocking operations on the same locks. (#56)
• Switch to a more efficient event notification mechanism. (#43)

Changelog

Sourced from async-lock's changelog.

Version 3.2.0

• Add missing methods for blocking on locking with types wrapped in Arc (#71).

Version 3.1.2

• Bump event-listener to version v4.0.0. (#69)

Version 3.1.1

• Add a note to the documentation comparing this crate against libstd's locks. (#58)

Version 3.1.0

• Add a Default implementation for OnceCell (#63).

Version 3.0.0

• Breaking: Add an enabled-by-default std feature that allows using this crate without the standard library. (#43)
• Support blocking and non-blocking operations on the same locks. (#56)
• Switch to a more efficient event notification mechanism. (#43)

Commits

• 37ccc91 v3.2.0
• d1cff63 Add missing Arc blocking methods (#71)
• 751c7b8 v3.1.2
• d333a41 Update event-listener requirement from 3.0.0 to 4.0.0 (#69)
• 9c7f6ef v3.1.1
• b9aa294 Fix broken links in docs
• 780e86b Check docs in CI
• 48c091e docs: Add a note comparing against std types
• 2d0c2ed v3.1.0
• 902e8f9 Implement Default for OnceCell (#63)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[DieracDelta]

I think that order to upgrade async-lock, we'll need to bump async-lock in tide disco first. I tried to do this a week ago and the trait name changed (or the trait was moved? not sure). Now when I compile I get:

error[E0277]: the trait bound `async_lock::RwLock<WebServerState<KEY>>: WriteState` is not satisfied
   --> crates/web_server/src/lib.rs:871:15
    |
871 |     let api = define_api(&options).unwrap();
    |               ^^^^^^^^^^ the trait `WriteState` is not implemented for `async_lock::RwLock<WebServerState<KEY>>`
    |
    = help: the following other types implement trait `WriteState`:
              async_lock::mutex::Mutex<State>
              async_lock::rwlock::RwLock<State>
              Arc<W>
              ()
note: required by a bound in `define_api`
   --> crates/web_server/src/lib.rs:682:48
    |
680 | fn define_api<State, KEY>(options: &Options) -> Result<Api<State, Error>, ApiError>
    |    ---------- required by a bound in this function
681 | where
682 |     State: 'static + Send + Sync + ReadState + WriteState,
    |                                                ^^^^^^^^^^ required by this bound in `define_api`

error[E0277]: the trait bound `async_lock::RwLock<OrchestratorState<KEY, ELECTION>>: WriteState` is not satisfied
   --> crates/orchestrator/src/lib.rs:246:15
    |
246 |     let api = define_api().map_err(|_e| io::Error::new(ErrorKind::Other, "Failed to define api"));
    |               ^^^^^^^^^^ the trait `WriteState` is not implemented for `async_lock::RwLock<OrchestratorState<KEY, ELECTION>>`
    |
    = help: the following other types implement trait `WriteState`:
              async_lock::mutex::Mutex<State>
              async_lock::rwlock::RwLock<State>
              Arc<W>
              ()
note: required by a bound in `define_api`
   --> crates/orchestrator/src/lib.rs:194:48
    |
191 | fn define_api<KEY: SignatureKey, ELECTION: ElectionConfig, State>(
    |    ---------- required by a bound in this function
...
194 |     State: 'static + Send + Sync + ReadState + WriteState,
    |                                                ^^^^^^^^^^ required by this bound in `define_api`

[shenkeyao]

We decided to not fix the CI and close this PR.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.