Remove more charmstore query data

[ChrisMacNaughton]

Additionally, makes two of the fields on-demand only, as libcharmstore nor amulet actually reference them. The API remains unchanged but the amount of data requested from the charmstore should be dramatically reduced.

[gnuoy]

LGTM. As you said @ChrisMacNaughton there is a risk of someone accessing self.raw directly but I think its a risk worth taking.

[johnsca]

Oh, I also meant to ask... This wraps theblues, but why is the wrapper necessary rather than just using theblues directly? Is it just to provide a nicer API? I was also under the impression that theblues was basically unmaintained; if this is maintained and used, would it make more sense to fold the actual request logic into this as well? If nothing else, the name is way better.

[ChrisMacNaughton]

I'm very much +1 to updating libcharmstore to handle the charmstore API rather than using theblues

[marcoceppi]

@johnsca At the time this library was created theblues didn't really have a good public interface. If theblues is unmaintained then we may want to consider folding request logic into this as well. We're still woefully young in the library's release cycle (0.0) so planning a 1.0 with request logic folded in and improvements to some of the less mature parts of the API would be great.