nova: take account of trace control area memory costs in vm session

Currently, the cap and ram quota isn't considered for allocations of the Trace::Control_area during the vm session construction on top of nova. I was wondering about core's unconstrained ram allocator being handed over into the Control_area's constructor, although a constrained ram allocator with the session's cap and ram quota exists.