[Storage] Removal of Requirement that Data Partition ID is the first component of the Kind property
As part of integrating with the new Schema Service (see indexer-service#7 (closed)), it was realized that a change of behavior is needed in the Storage service treatment of the "kind" property. Previously, it was required that data-partition-id was the first component of the "kind" property (i.e. data-partition-id:source:entitytype:version). However, with the Schema Service, there can be cross-partition schema authorities that should not be the data-partition-id.
An example of this would be "OSDU:wks:wellbore:". Here, "OSDU" is not a data-partition-id, but an authority that spans data partition concerns. To use this Schema scoping paradigm, Storage service needs to relax the check so that kind first component != data-partition-id destination for the storage record.