There's a minor tweak to the protocol, which I'm uncertain
is backwards compatible, so this becomes v4 of the MagicMotion
protocols.

This change reverses the device attributes so that just the vibe
may be exposed (the device config is updated to reflect this).

I do wonder if this initializer only change could have been amended
to the original protocol, but this since the initialisation is
distinctly different, it resides in a new protocol.

Bumps [url-parse](https://github.com/unshiftio/url-parse) from 1.5.3 to 1.5.10.
- [Release notes](https://github.com/unshiftio/url-parse/releases)
- [Commits](https://github.com/unshiftio/url-parse/compare/1.5.3...1.5.10)

---
updated-dependencies:
- dependency-name: url-parse
dependency-type: indirect
...

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

Bumps [prismjs](https://github.com/PrismJS/prism) from 1.25.0 to 1.27.0.
- [Release notes](https://github.com/PrismJS/prism/releases)
- [Changelog](https://github.com/PrismJS/prism/blob/master/CHANGELOG.md)
- [Commits](https://github.com/PrismJS/prism/compare/v1.25.0...v1.27.0)

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

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

Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.14.7 to 1.14.8.
- [Release notes](https://github.com/follow-redirects/follow-redirects/releases)
- [Commits](https://github.com/follow-redirects/follow-redirects/compare/v1.14.7...v1.14.8)

---
updated-dependencies:
- dependency-name: follow-redirects
dependency-type: indirect
...

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

Otherwise we'll fail the schema

Unsafe send/sync was unneeded, but requires switching json schema
libraries because valico isn't safe for send/sync (uses RefCell returns)

Implement a protocol that just passes json straight through to the
device implementation. Also make more things serializable for
usages with this (for device simulation)

This isn't really an error, as we can drop before we finish connecting,
or before a device dies.

These devices don't support the 'DeviceType;' command
and don't always advertise their LVS-* names properly either.
But they do advertise the non-standard 0xffb0 service.

Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.13.0 to 1.14.7.
- [Release notes](https://github.com/follow-redirects/follow-redirects/releases)
- [Commits](https://github.com/follow-redirects/follow-redirects/compare/v1.13.0...v1.14.7)

---
updated-dependencies:
- dependency-name: follow-redirects
dependency-type: indirect
...

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

Bumps [mermaid](https://github.com/knsv/mermaid) from 8.11.0 to 8.13.8.
- [Release notes](https://github.com/knsv/mermaid/releases)
- [Changelog](https://github.com/mermaid-js/mermaid/blob/develop/docs/CHANGELOG.md)
- [Commits](https://github.com/knsv/mermaid/compare/8.11.0...8.13.8)

---
updated-dependencies:
- dependency-name: mermaid
dependency-type: direct:production
...

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

Been a while, just reshuffle some things.

Change a bunch of messages from error to warn, since they may happen and
are good to know about but don't really affect operation (websockets will
error on disconnect, lovense dongle sends messages are weird times)

Will allow us to start watching for older windows versions in the logs,
as windows-rs doesn't play well with interface bindings sometimes.

This will show us whether or not certain DCMs can scan in the logs, as well
as warning users when they have conflicting DCMs, without having to
explicitly disable them in the library.

Fixes #416

We had more issues with type misalignment, so just ignore fields we
don't actually use.

Fixes #417

Show their number as part of their name that is sent to the client.

Otherwise it'll block the write thread during timeouts.

Fixes #420

Remove "Insecure" from log messages since it sounds worse than it is, add
more device manager logging for protocol and DCM addition

These will rarely change, and Desktop should handle updating them
as needed. We can reimplement this once desktop has better updating,
but there are no plans to change the format at the moment that would
break old versions.

Update device config and protocol for naming of known Satisfyer devices.

Satisfyer toys will stop communicating if they don't get a command for a
certain length of time. Keep sending updates to make sure that doesn't
happen. Also, truncate received name to remove null character.

The old protocol system was far too rigid in what we were allowed to do
during protocol construction, which caused issues trying to implement
update timers for Satisfyer. With a combination of macros and new
convenience functions, we get more flexilibity in construction while
also reducing boilerplate.

Finding a middle ground between copypasta and macro complication

We were just returning false (never scanning) before.

No wasm pipes :c