OCM: Separate storage resource from shared resource and add filters on received shares

[rawe0]

• Adds filters depending on share type to received OCM shares
• Deprecation of resource_type in favor of shared_resource_type, with change of type
• Deprecation of share_type in favor of recipient_type
• The OCMCore API remains unchanged since this is to be deprecated.

[glpatcern]

Some rephrasing in the comments

[glpatcern]

This change introduces an important clarification and separation of concerns: an incoming OCM share may grant access to a remote resource, which does not necessarily map to a storage resource, hence the resource_type must not be a storage ResourceType.

@butonic @micbar @2403905 @aduffeck as this is a(nother) breaking change I seek your review/approval as well. We believe it is worth the effort, given the above.

[glpatcern]

Let's go with this rename as agreed, and if no comments we merge

[2403905]

I'm ok with renaming

[glpatcern]

Thanks @rawe0 for all the reshuffling. I think this is good to go:

• The already deprecated ocm_core_api is left untouched
• The new types and fields are declared at the end, and corresponding old fields are flagged deprecated
  Going forward, we shall drop any deprecated field or type once we move to v1.0.0

[glpatcern]

@butonic any further comment on this? We'd like to merge this by end of day today