Bluesky

This release fixes small bugs in v1.0.0 and introduces one new feature. The API changes or deprecations are not expected to affect many users.

Enhancements
* Add a new command to the [RunEngine](http://nsls-ii.github.io/bluesky/run_engine_api.html#bluesky.run_engine.RunEngine), `'drop'`, which jettisons the currently active event bundle without saving. This is useful for workflows that generate many readings that can immediately be categorized as not useful by the plan and summarily discarded.
* Add `install_kicker()`, which dispatches automatically to `install_qt_kicker()` or `install_nb_kicker()` depending on the current matplotlib backend.

Bug Fixes
* Fix the hint for [inner_product_scan()](http://nsls-ii.github.io/bluesky/generated/bluesky.plans.inner_product_scan.html#bluesky.plans.inner_product_scan), which previously used a default hint that was incorrect.

API Changes
* In [tune_centroid()](http://nsls-ii.github.io/bluesky/generated/bluesky.plans.tune_centroid.html#bluesky.plans.tune_centroid), change the meaning of the `step_factor` parameter to be the factor to reduce the range of each successive iteration. Enforce bounds on the motion, and determine the centroid from each pass separately.
* The [SupplementalData](http://nsls-ii.github.io/bluesky/plans.html#bluesky.preprocessors.SupplementalData) preprocessor inserts its instructions in a more logical order: first baseline readings, then monitors, then flyers. Previously, the order was reversed.

Deprecations
* The suspender `SuspendInBand` has been renamed to [SuspendWhenOutsideBand](http://nsls-ii.github.io/bluesky/generated/bluesky.suspenders.SuspendWhenOutsideBand.html#bluesky.suspenders.SuspendWhenOutsideBand) to make its meaning more clear. Its behavior has not changed: it suspends when a value exits a given range. The original, confusing name now issues a warning.
* The suspender `SuspendOutBand`, which counter-intuitively suspends when a value enters a given range, has been deprecated. (If some application is found for this unusual scenario, the user can always implement a custom suspender to handle it.)

This tag marks an important release for bluesky, signifying the conclusion of the early development phase. From this point on, we intend that this project will be co-developed between multiple facilities. The 1.x series is planned to be a long-term-support release.

Bug Fixes
* `mv()` and `mvr()` now works on pseudopositioners.
* `reset_positions_wrapper()` now works on pseudopositioners.
* Plans given an empty detectors list, such as `count([])`, no longer break the `BestEffortCallback`.

Full release notes are on our [documentation website](https://nsls-ii.github.io/bluesky/api_changes.html#v0-11-0)

We are proud to announce the 0.10.0 release of bluesky.

* Automatic best-effort visualization and peak-fitting is available for all plans, including user-defined ones.
* The “SPEC-like” API has been fully removed, and its most useful features have been applied to the library in a self-consistent way. See [here](https://nsls-ii.github.io/bluesky/api_changes.html#api-changes) for detailed instructions on migrating.
* Improved tooling for streaming documents over a network for live processing and visualization in a different process or on a different machine.

Full release notes are on our [documentation website](https://nsls-ii.github.io/bluesky/api_changes.html#v0-10-0)