Moved to docs site. We'll still keep spec bugs here tho.

This was a book I started 3 years ago and never touched again.

Fixes #431 by both wildcarding the Iker name and using the manufactuerer
data as fallback for matching with CSR4, etc dongles.

Thanks to mumble for confirming the protocol details

Thanks to mumble for info

These have never been used, and introducing them now would be
very confusing to end users.

These have not really worked correctly for years, and I was just using
them as the base for tests, which was confusing to users. Just point
users at the dev guide, and put test utilities in the test directory.

Allows us to modify messages after they've been filled out but before
they're distributed. Used for filling in indexes in DeviceAdded/Info
messages.

Will be used for array shimming for indexes.

The battery field needs to be able to handle when the JSON field for it is null.

Because when a toy connects, Lovense Connect will send null in the battery field
until the toy has been fully initialized im guessing?

In my opinion Lovense Connect should just send 0 instead of sending null when a toy isnt fully initialized.

However the bug behaviour is:
1. Connect a ButtplugClient
2. Start Lovense connect
3. Connect toy to Lovense Connect
4. Call ButtplugClient::start_scanning()
5. The json deserialization will fail and will not parse the incoming connected toy.
6. Scan again and you will get the battery number.

Untested. Tests for Olis and Cali to complete

Bumps [express](https://github.com/expressjs/express) from 4.17.1 to 4.18.2.
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/master/History.md)
- [Commits](https://github.com/expressjs/express/compare/4.17.1...4.18.2)

---
updated-dependencies:
- dependency-name: express
dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Bumps [qs](https://github.com/ljharb/qs) from 6.5.2 to 6.5.3.
- [Release notes](https://github.com/ljharb/qs/releases)
- [Changelog](https://github.com/ljharb/qs/blob/main/CHANGELOG.md)
- [Commits](https://github.com/ljharb/qs/compare/v6.5.2...v6.5.3)

---
updated-dependencies:
- dependency-name: qs
dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Bumps [decode-uri-component](https://github.com/SamVerschueren/decode-uri-component) from 0.2.0 to 0.2.2.
- [Release notes](https://github.com/SamVerschueren/decode-uri-component/releases)
- [Commits](https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.0...v0.2.2)

---
updated-dependencies:
- dependency-name: decode-uri-component
dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Previously Hgod devices would start but never stop

There's still 3 Hismith devices unaccounted for:
* Sinloli - A suction/vibrator onahole
* Eropair - An onahole and a rabbit, possibily paried somehow?

If the PnP characteristic isn't 6 bytes, it's not a BT MAC,
so we'll assume that no handshake is needed.

Tested on a bunch of Roselex's including one of the pill models
that doesn't require a handshake.

This includes via Lovense Connect
Some other Lovense devices were corrected in the connect protocol definition

Fixes #506

This doesn't address LovenseConnect as that's waiting on a different PR

The way we were doing match all meant
that devices that need full command packets
weren't dismissing repeated commands.

Fixes #532

Both broken in different ways in Buttplug tho.