refactor!: Drop AsyncTryReadWriteBytes and TryReadWriteBytes traits, revert to standard Read + Write, AsyncRead + AsyncWrite

[theangryangel]

The purpose of this is to unlock something for #158. Without doing this we basically get stuck in a position where any new stream needs to be dealt with by the library.

Fundamentally I had a misunderstanding of the actual issue in #94.

Outcome of this:

• Original Framed enum for tokio and blocking implementations are replaced with a what was FramedInner, however the inner stream is now boxed.
  • Sidebar why boxing? To make returning different implementations from a match statement or method easier for consumers of the library. There is a perf hit, but practically it's not relevant.
• This allows for potentially any standard Read + Write stream for the blocking implementation. i.e. a file reader.
• This allows for any AsyncRead + AsyncWrite stream for tokio implementation
• Simplifies the consumption of the builder for end users
• Removes any confusion and maintenance over the "inner" and outer frames by reducing the amount of code.
• Removes the dependency on async_trait, therefore Remove async_trait macro in favor of AFIT & RPITIT #123 is no longer relevant

Additional extras bundled into this PR:

• Setter methods for IsiFlags on builder feat: add convenience methods to builder to set ISI flags #186

Migration for end users:

• If you were matching on or generating the Framed type, you'll need to update what you're doing. Otherwise, probably nothing.

Outstanding work:

• Make UdpStream safe (needs an internal inner buffer like the WebSocket implementation)
• Remove the try_read_bytes temporary methods in both blocking and tokio implementations of Framed
• Fix any relevant documentation
• Break up blocking_impl/mod.rs like tokio_impl/mod.rs