Implicit elision of type lifetime parameters is deprecated, as per the
rust-2018-idioms warning.

Clippy's needless_pass_by_value lint shows a couple functions that don't
need to own their arguments. undeploy() in particular takes a 240-byte
Options struct by value but, like deploy(), doesn't need mutable access.

Clippy's unnested-or-patterns lint caught this.

Clippy's match-same-arms lint caught this. The previous two functions
already used or-patterns like this, but condition() was overlooked.

Clippy's unused-self lint caught this.

Clippy's doc-markdown lint caught this.

Due to being in a move closure, this clone captures opt by value and
then clones it. This wouldn't work even if opt were used later in the
enclosing scope and serves no purpose as it is.

Clippy's uninlined-format-args lint caught this.

Clippy's redundant-else lint caught this.

Rustfmt wants this broken due to line length and requires {} for
multiline match arms, but doesn't insert a ; because it only sees
syntax, not types. Clippy then complains (when pedantic) about the
implicit () return.

Clippy's clippy::semicolon-if-nothing-returned lint caught this.

Clippy's redundant-closure lint caught this.

Replaces `assert_eq!(x, [true|false])` with `assert!([x|!x])`.

Clippy's bool-assert-comparison lint caught this.

When testing without the `scripting` feature, compilation would fail
because a `Configuration` was constructed assuming the `helpers` field
always exists, but it only exists when `scripting` is enabled.

In `deploy::test::{low_level_simple, low_level_skip}`,
`Default::default()` was used to construct a `BTreeMap`, with the only
indication of the variable's type being the signature of
`RealActionRunner::new()`, which it was passed by reference to.

Clippy's default-trait-access lint caught this.

This is less verbose and provides a more detailed panic message.

`config::tests` was the only test module not named `test`.