Add: json_schema feature

[RaulTrombin]

Details:
Add json schema feature for PingProtocol definitions,

tested on PingViewerNext:

Details of jsonschema:
message_schema.json

...
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Messages",
  "oneOf": [
    {
      "type": "object",
      "properties": {
        "Bluebps": {
          "$ref": "#/$defs/Messages"
        }
      },
      "additionalProperties": false,
      "required": [
        "Bluebps"
      ]
    },
    {
      "type": "object",
      "properties": {
        "Omniscan450": {
          "$ref": "#/$defs/Messages2"
        }
      },
      "additionalProperties": false,
      "required": [
        "Omniscan450"
      ]
    },
    {
      "type": "object",
      "properties": {
        "Ping1D": {
          "$ref": "#/$defs/Messages3"
        }
      },
      "additionalProperties": false,
      "required": [
        "Ping1D"
      ]
    },
    ...

[joaoantoniocardoso]

"$ref": "#/$defs/Messages"
"$ref": "#/$defs/Messages2"
"$ref": "#/$defs/Messages3"
...

Coudln't this have a better naming, maybe something like "BluebpsMessage", etc?

[RaulTrombin]

"$ref": "#/$defs/Messages"
"$ref": "#/$defs/Messages2"
"$ref": "#/$defs/Messages3"
...

Coudln't this have a better naming, maybe something like "BluebpsMessage", etc?

I didn't notice the numerations. In fact, we have a set of Messages for each structure, so schemars automatically indexed it, which was smart haha.

https://docs.bluerobotics.com/ping-rs/bluerobotics_ping/ping1d/enum.Messages.html

Let me check if we can change just the ref IDs to something from our builder/macro.

[RaulTrombin]

@joaoantoniocardoso seems it breaks all other generated refs.

[RaulTrombin]

@joaoantoniocardoso did it, just let me organize it

[RaulTrombin]

message_schema.json

[joaoantoniocardoso]

Nice job, I have just some small (and optional) suggestions :)

[joaoantoniocardoso]

We could use tmp dir here (not tested):

        let mut path = std::env::temp_dir();
        path.join(filename);
        let mut file = std::fs::File::create(&path).unwrap();

But I see that for manual inspection, it can be useful to create it in an more easily accessible place. In this case, you can add a "tests/tmp" folder to ".gitignore" and use it instead (not tested):

        let mut path = std::fs::Path::new("tests/tmp").unwrap();
        create_dir_all(path).unwrap();
        path.join(filename);
        let mut file = std::fs::File::create(&path).unwrap();

obviously, the load_schema function would have to adapt.

[RaulTrombin]

Approach 2 seems good, we can improve this afterward with some WASM example

[RaulTrombin]

ping @patrickelectric