Ship a 1.0 release

[thejpster]

Part of rust-embedded/wg#383

Add blocking issues here:

• can run cargo test neither on stable nor on unstable - Cannot run the tests in continuous integration #24
• Review against https://rust-lang.github.io/api-guidelines/ - Pre-1.0 API guidelines review #31
• Document MSRV - Document current MSRV #30
• Remove unstable feature - Remove unstable feature and code and modernize #32
• CI on GHA + bors - Switch from travis to Github Actions and setup bors #23 Cannot run the tests in continuous integration #24
• Only include await! in Rust nightly via build.rs? - Only include the await! macro when compiling with nightly Rust #28
• Bump version in cargo.toml - Prepare 1.0.0 #33
• Add version section in changelog - Prepare 1.0.0 #33
• Release 0.1.3 semver-trick version - Prepare v0.1.3 semver-trick release for nb 1.0 #34
• 🎉

[hannobraun]

I guess the main blocking issue would be, whether this crate offers the right approach at all, and whether/how it needs to change (or be discarded completely) in the face of the async stuff that already landed in Rust, and is yet to come. See #14, rust-embedded/embedded-hal#149, and rust-embedded/embedded-hal#172.

[eldruin]

I would nominate #22 for this.

[eldruin]

Further TODOs:

• Review against https://rust-lang.github.io/api-guidelines/
• Remove unstable feature
• CI on GHA + bors - Switch from travis to Github Actions and setup bors #23 Cannot run the tests in continuous integration #24
• Only include await! in Rust nightly via build.rs?

[jonas-schievink]

• Remove unstable feature
• Only include await! in Rust nightly via build.rs?

I prefer the current approach of having to opt into unstable features. It mirrors how unstable features in Rust work, and if we automatically enable unstable feature for nightly Rust versions people could accidentally start using an unstable feature in this library just because their installation happens to default to the nightly Rust channel (which is a reasonable thing to do in order to use unstable compiler flags and benefit from recent performance improvements, etc.).