add spaceID to resourceID

[micbar]

Description

To correctly address storage spaces in reva, we need another id property on the resourceID.

This change is not breaking and should be compatible for the master and the edge branches.

1. masterbranch.

We do not need to change anything

2. edge branch

Currently the storageID attribute is used for a concatenated <storageproviderID>$<spaceID>

With this change, we will be able to separate them and have a clean implementation back.

@labkode @glpatcern I will also update the cs3apis on the master branch to keep everything on the same version of the apis.

[labkode]

@micbar I agree with @kobergj and @glpatcern that this field MUST be an optional field for time being.
Apart from ownCloud, no one is using the SpacesAPI for their reference implementation.

[kobergj]

@micbar @butonic @labkode @glpatcern How about we add a new OPTIONAL StorageProviderID and use the StorageID as SpaceID in ocis? That is basically the way ocis does it now too anyways.

[micbar]

@micbar I agree with @kobergj and @glpatcern that this field MUST be an optional field for time being.
Apart from ownCloud, no one is using the SpacesAPI for their reference implementation.

That surprises me.

I thought we have an agreement that spaces are the first class citizens in the API.

[micbar]

@micbar @butonic @labkode @glpatcern How about we add a new OPTIONAL StorageProviderID and use the StorageID as SpaceID in ocis? That is basically the way ocis does it now too anyways.

That is what ocis does today and IMO not clean. See the original description of storage_id which means exactly the provider.

[micbar]

@labkode @glpatcern I changed the REQUIRED flag to OPTIONAL. Not a blocker for me.

Please let us continue here.

[glpatcern]

@micbar I think it's the best option at this point in time, leaving the door open to both approaches. Will merge.