Early on, we decided to make context always a parameter to remotable
methods. If the caller passed a context, we'd use that, and if not,
we'd use the one stored on the object if possible. That has been
not that useful, and also a source of infinite confusion for people
learning the code. One of the work items here is to remove that
ambiguity and require that the object have an embedded context in
order to make any remotable calls.
Change-Id: I6ee4404f3b16c5cb8db93db13eb75e1aa1a3c146
5e79ffca1d