Update mockall requirement from 0.7 to 0.10 in /language-server

[dependabot-preview]

Updates the requirements on mockall to permit the latest version.

Changelog

Sourced from mockall's changelog.

[ 0.10.0 ] - 2021-06-27

Added

• mock! will now allow both methods and trait impls to be gated with #[cfg()]] attributes. The attributes will be forwarded to all generated code. This allows for example only mocking certain traits on certain OSes. (#297)

• automock will now automatically generate Debug implementations for traits and structs. mock! will to, if you put #[derive(Debug)] above the struct's name. (#289)

• Added support for specific impls. A specific impl is an implementation of a trait on a generic struct with specified generic parameters. For example, impl Foo for Bar<i32> as opposed to impl<T> Foo for Bar<T>. Mockall does not yet support generic methods in such traits. (#274)

Changed

• Mockall is pickier now about how you mock a trait on a generic struct. Previously you could usually omit the generics. Now, they're required. i.e.,

  mock!{
      MyStruct<T: Bounds> {...}
      impl Foo for MyStruct {...}
  }

  should now be written as

  mock!{
      MyStruct<T: Bounds> {...}
      impl<T: Bounds> Foo for MyStruct<T> {...}
  }

  (#274)

Fixed

• Fixed setting simultaneous expectations with different generic types on generic methods whose generic parameters appear in neither the arguments nor the return type. (#272)

[0.9.1] - 2021-02-13

Added

... (truncated)

Commits

• d8e2ec3 Explicitly specify the path to the serde example
• 75b2beb (cargo-release) version 0.10.0
• 3228fb7 (cargo-release) version 0.10.0
• 543eef9 [skip ci] remove "upload-doc" from release.toml
• 50e95a3 Merge pull request #297 from asomers/cfg
• 7ff1e03 Allow #[cfg()] attributes on trait impls in mock!
• 8076cd4 Merge pull request #289 from asomers/autodebug
• 5b993d5 fix a typo in an error message
• f367875 Automatically generate Debug impls for mock structs
• 066c044 fix a typo in CHANGELOG
• Additional commits viewable 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)
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

• Update frequency
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)