Support service definition renames

[gberche-orange]

Expected behavior

• As an osb-cmdb operator
• In order to support catalog changes such as service definition renames (e.g. Service Offering name p-mysql becomes mariadb)
• I need the cmdb to transparently update its inventory upon such catalog change

Observed behavior

Backend service instances are created in space named after the service definition name. Upon service definition name change:

• existing backend services are not found anymore by cmdb, resulting in 404, 400, or 410 OSB API errors for USI,DSI,CSB,DSB
• new instances trigger the creation of a new backing space with the current service definition name

Affected release

Reproduced on version 0.x

Possible fixes

• Keep the backing service space consistent with service offering
  • manually, see https://github.com/orange-cloudfoundry/paas-templates/issues/787
  • automatically ??
• Use a fallback to lookup backing services by guid using metadata
  • Attach metadata label to backing service spaces:
    • backing-service-definition-id
    • brokered-service-definition-id
  • When no space is found matching the service definition name:
    • lookup an existing space by label backing-service-definition-id
    • rename that space with the current service definition name

[gberche-orange]

Setting to low priority since a manual rename of the backing service space might sufficient.