Clarify how to model binary data (3.2.0)

This reorganizes binary data-related guidance into a
"Working With Binary Data" section, as has already been
done in 3.0.4.

This includes more detailed guidance on when various
approaches to binary data make sense (e.g. you cannot
stuff raw binary into JSON no matter what you put in your
Schema Object, and while you can base64-encode entire
message bodies, it takes up a lot more space for no clear
benefit).  An example that contradicts this guidance has
been removed.

The lack of and HTTP header for base64 encoding is now
explicitly called out.

Also note that only `multipart` media types with named parts
are supported, as they are modeled as an object.