Update rusty_pool requirement from 0.6 to 0.7

[dependabot]

Updates the requirements on rusty_pool to permit the latest version.

Changelog

Sourced from rusty_pool's changelog.

[0.7.0] - 2022-05-05

• improve joining
  • use wait_while and wait_timeout_while to protect against spurious wakeups
  • add join_generation field to WorkerData to make sure all threads waiting for a join leave at once by having the first awakened thread increment the counter
    • otherwise the pool might become non-idle again before all notified threads were awakened, causing them to keep waiting
• implement ThreadPool::start_core_threads
  • starts all core workers by creating core idle workers until the total worker count reaches the core count
  • implement WorkerCountData::try_increment_worker_count as an alternative to try_increment_worker_total allowing to specify a custom increment
  • replace INCREMENT_TOTAL + INCREMENT_IDLE with INCREMENT_TOTAL | INCREMENT_IDLE as a bitwise or is enough to combine the increments as they have no overlapping bit and addition is not required
• make field JoinHandle.receiver public

[0.6.0] - 2021-05-02

• replace Atomic64 with AtomicUsize for worker count bookkeeping
  • refactor worker count bookkeeping arithmetics to work based on the size of usize on a given platform instead of requiring 64 bits
  • enables using the crate on non 64 bit platforms

[0.5.1] - 2021-02-27

• Replace compare_and_swap with compare_exchange_weak.
  • compare_and_swap has been deprecated as of rust 1.50.0

[0.5.0] - 2021-01-30

• Instead of incrementing the worker total and using the returned previous value to check if the worker is still required and then decrementing the counter again if that's not the case, use a compare and swap mechanism implemented by WorkerCountData::try_increment_worker_total to increment the total count if the current workerCountData matches the expected value and retry until it succeeds or until the observed value reaches the provided maximum value (either the core pool size when attempting to create a core worker, else the max pool size), at which point the pool proceeds to creating a non-core worker or to sending the task to the channel.
  • This only requires one atomic operation per retry instead of 2 (if contention is high it may lead to more retries as increments could not fail before but retries are much cheaper as it does not have to decrement the counter and recursively call the method) and

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 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)