juwang-enable virtual core in Java Reef and clr bridge

Currently Reef clients cannot set virtual core when they request evaluators. This PR is to enable the virtual core in EvaluatorRequest so that the clients can set core count when an EvaluatorRequest is created.  
The request is submitted through EvaluatorRequstor and eventually reaches to ResourceRequestHanlder and set to Resource object. ResourceRequestProto schema is updated for this.
After a Container is allocated, the core data is passed back from YARN. ResourceAllocationProto and EvaluatorDescriptor are also modified to hold the data. 
Submit() in EvaluatorRequestorBridge is updated to add this parameter. All clr bridge related methods are also modified accordingly. 

This is for #995

Yes. Just for showing a sample purpose. Default is 1.

From: Markus Weimer [mailto:notifications@github.com]
Sent: Thursday, September 25, 2014 8:13 AM
To: Microsoft-CISL/REEF
Cc: Julia Wang (QIUHE)
Subject: Re: [REEF] juwang-enable virtual core in Java Reef and clr bridge (#1002)


In reef-examples/src/main/java/com/microsoft/reef/examples/hello/HelloDriver.java:

> @@ -60,6 +60,7 @@ public void onNext(final StartTime startTime) {

>        HelloDriver.this.requestor.submit(EvaluatorRequest.newBuilder()

>            .setNumber(1)

>            .setMemory(64)

> +          .setCore(1)

whenever the number of cores requested is 1, we can ommit the call to setCore(), right?

—
Reply to this email directly or view it on GitHub<https://github.com/Microsoft-CISL/REEF/pull/1002/files#r18037645>.