Improve the error details when accessing missing resource attributes.
Review Request #10383 — Created Jan. 14, 2019 and submitted
When attempting to access an attribute that doesn't exist on a resource,
the caller would just get a plain
AttributeError. Left uncaught, this
would be displayed to the user, making it very hard to report anything
This change adds explicit error information containing the attribute
being requested and the resource it's being requested on.
Used this to diagnose a separate problem. Saw the enhanced error details.