Potential settings object

@jebeck @skrugman @kentquirk 

This is a pull request with an example "settings" object.  I'm intending that any time even ***one*** of the data points in these items changes, we get a brand new object with ***all*** of the "current" values.  We will store the stream of all schedules that have existed.

Does this make sense to you?  It should be pretty straight-forward to generate this data from medtronic, I haven't dug into animas yet, though, so when I do get around to that, some things might change around.  I'm not planning on diving into animas until I'm done with medtronic stuff, though.  

Just from a high level, it seems like all pumps should have some measure of these ideas though.  The question for Animas will be more around if they expose the stuff to us or not.

Also, a point on organization of this repo.  I don't understand the organization of this repository and I just wanted to show an example file, so I put it here.  If you would rather this be somewhere else, just let me know (or feel free to just move it around).

On the names of the fields, I think they are intuitive and just make sense given the data we are working with.  I'm not attached to any of them though, if you want them changed or want an explanation of the data type, lmk.