Refactor asks and allocations to use consistent locking

In the core scheduler, the ask and allocation objects use inconsistent locking / access patterns. These should be refactored to use strong encapsulation (getters for read/only, getters/setters for mutable values using locks).