CloudFoundryAppDeployer should rebind SI after updating the SI when updateServiceInstance

[LittleBaiBai]

Currently in CloudFoundryAppDeployer, we rebind service instance before updating the service instance in the implementation of updateServiceInstance. The order doesn't seem right. We should write a failing test to reproduce the problem then fix the ordering.

@Override
public Mono<UpdateServiceInstanceResponse> updateServiceInstance(UpdateServiceInstanceRequest request) {
	return operationsUtils.getOperations(request.getProperties())
		.flatMap(cfOperations -> rebindServiceInstanceIfNecessary(request, cfOperations)
			.then(updateServiceInstanceIfNecessary(request, cfOperations)));
}

[royclarkson]

@LittleBaiBai do you have a scenario in mind where updating a service instance will result in it being unbound?

[LittleBaiBai]

@royclarkson I'm imagining a case where backing service params would influence the binding credentials that backing app receives from the backing app binding, and that's one of the reasons, if not all, why users would set rebind-on-update to true in their configuration. That's why I think we should do update before the rebind.