Bump Microsoft.Coyote from 1.4.3 to 1.7.0

[dependabot]

Bumps Microsoft.Coyote from 1.4.3 to 1.7.0.

Changelog

Sourced from Microsoft.Coyote's changelog.

v1.7.0

• Updated the default random exploration strategy with a portfolio testing mode that uses a tuned set of different exploration strategies to increase coverage for different bug patterns. The portfolio will be transparently enhanced over time as new exploration strategies become available inside Coyote. The Portfolio can be set to fair or unfair using Configuration.WithPortfolioMode or the --portfolio-mode command-line option. The portfolio mode can be disabled and explicitly set to one of the available exploration strategies by setting a strategy-related option such as Configuration.WithRandomStrategy or -s <STRATEGY>.
• Refactored the NuGet packages, by moving Microsoft.Coyote.Actors to its own dedicated package, introducing a new Microsoft.Coyote.Tool package that contains the self-contained coyote command-line tool (for users that do not want to manage coyote via the Microsoft.Coyote.CLI .NET tool), introducing a new Microsoft.Coyote.Core package that only contains the core runtime library of Coyote, and converting the Microsoft.Coyote NuGet package into a meta-package that pulls all non-tool packages.
• Moved the actor Event type under the Microsoft.Coyote.Actors namespace.
• Introduced a Monitor.Event type (nested in the Microsoft.Coyote.Specifications.Monitor class), which must now be used for declaring specification monitor events, instead of the original Event type above.
• Enhanced and streamlined the logging API and built-in loggers, which are now available in the Microsoft.Coyote.Logging namespace, instead of Microsoft.Coyote.IO.
• Removed support for the end-of-life net5.0 target framework.

v1.6.2

• Exposed new IActorRuntime.GetCurrentActorIds() API that returns the ActorId for each active actor managed by the runtime, as well as an IActorRuntime.GetCurrentActorTypes() API that returns the Type of each active actor managed by the runtime. These APIs are not thread-safe and should only be used for gathering statistics and debugging purposes.

v1.6.1

• Exposed new IActorRuntime.GetActorExecutionStatus(id) API that enables querying the actor runtime for the current execution status of the actor with the specified id, as well as an IActorRuntime.GetCurrentActorCount() API that returns the number of active actors managed by the runtime. These APIs are not thread-safe and should only be used for gathering statistics and debugging purposes.
• Exposed new IActorRuntime.OnActorHalted callback which is triggered when an actor has halted and the runtime has stopped managing it.

v1.6.0

• Exposed new Operation API that enables instrumenting, controlling and scheduling custom concurrent operations.
• Exposed new SchedulingPoint.SetCheckpoint API that allows to capture all non-deterministic decisions in the currently explored execution path and try replay them in subsequent test iterations to optimize coverage of a subset of the state space.
• Added support for intercepting and controlling asynchronous locks.
• Added support for rewriting the SemaphoreSlim type.
• The Configuration.WithReplayStrategy method was renamed to Configuration.WithReproducibleTrace to make it more explicit that setting this option allows reproducing the specified trace.
• Various runtime improvements and bug fixes.

v1.5.9

... (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)

[dependabot]

Superseded by #157.