Promises status .status.status can be renamed

[ChunyiLyu]

Promises have a .status.status field that can be set to either Available or Unavailable. We should think about renaming/refactor this field because status.status reads redundant and a bit awkward

status implies that there could be multiple state rather than Available or Unavailable. If all we want to express is if this promise is available or not, this can be better expressed as a bool, e.g. .status.available or .status.ready

[kirederik]

agree, a bit redundant;

the status field is, sometimes, "Error" or some other status. Any suggestion on how to deal with that (or how to make it look nice on k get promises)?