Propagate osb client platform name to backing service

[gberche-orange]

Expected behavior

As a 3rd party backing service provider

• in order to apply different processing based on the client platform identity (such as old school source IP adress filtering), in a service broker which can't read the OSB context such as pivotal/cloud-service-broker (see https://github.com/pivotal/cloud-service-broker/issues/138)
• I need to distinguish client platform in OSB service provisionning calls

Observed behavior

The x-osb-cmdb param includes OSB context and headers which propagates the osb-cmdb organization name in parameters.x-osb-cmdb.annotations.brokered_service_context_organizationName, which is not sufficient to identify a client platform tenant in the following cases

• the service broker framework isn't granting access to OSB context

Affected release

Reproduced on version 1.1.0

Proposed api

The x-osb-cmdb param includes an additional annotations.brokered_service_client_name field matching the osb-cmdb backing service org name (or potentially an opt-in property to make this name stable in time despite the org renaming)