Attributes description

### For review ONLY – do not merge

---

This PR is implementation of https://github.com/apiaryio/api-blueprint/pull/135 in the API Blueprint AST

### **TODO**

- [x] Extend AST to hold resolved assets and MSON subtrees
- [x] Better examples
- [ ] Source Maps

---

### Update

#### Resolved Properties
In addition to introducing Attributes sections into API Blueprint, this PR also proposes the extensions to API Blueprint AST to support API Blueprint parser / subsequent tools in the form of "resolved" object properties. 

Resolved properties (starting with the "resolved" prefix) are not generated by the parser itself as they do not depict the source blueprint, instead they MAY be generated by the parser harness (or other tools further downstream) to simplify some frequent operations with the API Blueprint AST. Currently, this covers

- Fully resolving (expanding) MSON subtrees in attributes description nodes
- Generating representations or schemas out of attributes description. 

#### YAML Examples
To keep the file manageable I have decided to remove the YAML example. I am considering removing YAML examples from other serializations documents as well (but still want to keep YAML as possible serialization format).


 Good eye @danielgtaylor, so the idea is to go from 

```
- body (string)
```

to 

```
- assets
    - body
        - source
        - resolved
```

eventually.

Reality is we will keep the old `body` there for some time. 

So it will be 

```

```
- body (string)
```

to 

```
- body (string) - same as assets/body/source
- assets
    - body
        - source
        - resolved
```

I have removed it out from the AST spec so nobody (who haven't already used) will use it (in a new tool). 

But maybe I should put it back and mark it deprecated for a better clarity? Thoughts?