Update dictionary JSON spec field names and examples

[jwest115]

Related Issue(s)
Has Unit Tests (y/n)
Documentation Included (y/n)

---

Change Description

• move arrays, structs, and enums into typeDefinitions
• rename formatSpecifier to format
• rename identifier to name
• shorten identifier to id
• add bool size

[LeStarch]

@bocchino you'll need to review this one!

[thomas-bc]

As I'm wiring fpp-to-dict in to the CMake system, figuring out how to specify libraryVersions is giving me some troubles. I think providing an example would be helpful. Here are my questions:

1. What is the format we want to use? libraryName=1.0.0, [email protected] , libraryName==1.0.0 etc... ? We probably need to add this to the spec.
2. Say the library name is very generic e.g. arduino-i2c, are we ok with it being impossible to figure out where the library came from unless we can look at the source project? What I'm hinting at here is we could have an optional field e.g. remoteUrl or something. I don't actually think it would be useful/beneficial, but I just wanted to double check with everyone.
3. How do we deal with unspecified versions? e.g. a user has created a library locally but it is not a git submodule and/or there is no version to be retrieved.

[jwest115]

This is a good point @thomas-bc. The format of entries in libraryVersions is not specified in the spec. Also, there is no check done in the fpp-to-dict tool to verify that the libraryVersions input conforms to a certain format.

[thomas-bc]

Just marking things as I notice them

[bocchino]

This PR looks good to me! It makes the changes we discussed.