Update memory/maxmem reading in Rapi backend
Update memory/maxmem reading in Rapi backend

Recent changes to the instance beparams have replaced memory with
maxmem in Rapi bulk queries. Until this is either reverted (for
backwards compat) or we decide to go ahead with only maxmem, we change
the backend to read both; this only affects the "instance down" code
path (where ``oper_ram`` is missing).

Signed-off-by: Iustin Pop <acf83a5274f31a43af6b914614365999469c1a31@google.com>
Reviewed-by: René Nussbaumer <bc755ac45a0e799d1d490cba76febc56d80cc5fc@google.com>

apyrgio/snf-ganeti,andir/ganeti,onponomarev/ganeti,leshchevds/ganeti,yiannist/ganeti,yiannist/ganeti,apyrgio/snf-ganeti,andir/ganeti,leshchevds/ganeti,bitemyapp/ganeti,dimara/ganeti,ganeti-github-testing/ganeti-test-1,dimara/ganeti,mbakke/ganeti,ganeti/ganeti,leshchevds/ganeti,ganeti/ganeti,grnet/snf-ganeti,mbakke/ganeti,andir/ganeti,onponomarev/ganeti,mbakke/ganeti,yiannist/ganeti,apyrgio/ganeti,ganeti/ganeti,grnet/snf-ganeti,ganeti-github-testing/ganeti-test-1,bitemyapp/ganeti,apyrgio/ganeti