Golem infrastructure properties in CreateTaskReply

[mfranciszkiewicz]

• ~follows the infrastructure property spec~ Edit: dropped as it introduces unnecessary complexity
• current primary use: provide the estimated min. required memory in CreateTaskReply

In the review please include your opinion on:

• ~including all of these inf properties instead of min memory only~ ~Any future infrastructural requirements (e.g. CPU core count) should also follow the spec.~ Edit: extra properties have been removed
• directly using the Infrastructure protobuf message (bad UX wise) The interface could require an Infrastructure dataclass instead. In messages we would transfer the Infrastructure as a JSON object. Doubling the message in dataclasses seems to be an overkill.

[mfranciszkiewicz]

I've limited the scope of available properties.

@maaktweluit Strongly typed as in the pb message or a separate dataclass? For messages, you cannot directly assign properties which are messages and have to use the CopyFrom method. E.g. CreateTaskReply.inf_requirements.CopyFrom(inf)

[mfranciszkiewicz]

I've introduced the requested changes. It's taking substantially too much effort to introduce 1 extra returned value.

@Wiezzel @maaktweluit Please re-review.