Also adding name for Emma Neo

Fixed the name of the Svakom Lite Neo too

This is a BT2 serial rotation controller that doesn't
have a reverse mode, so it's mapped as a scalar rotator.

The 2 outputs are not indivually controlled.

The device registers 2 RFCOMM ports, only the second seems
to allow connections.

Whilst I'm able to write to the device, I'm not getting any
response, but sirah on Discord confirmed that it worked for
them.

No tests, as I don't see an easy way to test serial devices.

Broke when I removed docs

Fixes #534

These devices don't send name advertisments properly (not sure why), so we were
using the advertised service 0xffb0, but that conflicted with the Hismith devices.

This fix uses the manufacturer data: I'm hoping the company will be rare 0x026c,
because only the first 2 bytes of the actual data array seem to be consistent...

Also reverting d923726 which added a duplicate Chorus definition as a
WeVibe4 (it was discovered that the Chorus was an oddball and got its
own protocol implementation in 4a2fb619)

Bumps [json5](https://github.com/json5/json5) from 2.2.0 to 2.2.2.
- [Release notes](https://github.com/json5/json5/releases)
- [Changelog](https://github.com/json5/json5/blob/main/CHANGELOG.md)
- [Commits](https://github.com/json5/json5/compare/v2.2.0...v2.2.2)

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

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

Bumps [json5](https://github.com/json5/json5) from 2.2.0 to 2.2.2.
- [Release notes](https://github.com/json5/json5/releases)
- [Changelog](https://github.com/json5/json5/blob/main/CHANGELOG.md)
- [Commits](https://github.com/json5/json5/compare/v2.2.0...v2.2.2)

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

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

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.