Writable volume to be provided as a readyOnly volume to a container orchestrator?

[lpabon]

From @adityadani 's comment on #207:

@jvinod This could be a separate discussion, but do we want a writable volume to be provided as a readyOnly volume to a container orchestrator? Some drivers will not have a notion of readOnly volumes.

However if we allow, then we defer the control to CO then it might schedule apps which perform write operation on such a volume.

[lpabon]

I'll create a table which will define how this function will return information to the CO