adding go-cfclient

[sleungcy]

@Cocossoul @loafoe

• I added the dependency to go-cfclient, and an authenticated instance of it into runbinder.
• Added initial upgrade to v3 for resource_cf_route_service_binding through using the go-cfclient.

[Cocossoul]

Since api v3 the route service binding ID was introduced. It is a breaking change but I think it would be best if the resource ID is the route service binding ID, and not the combination of route id and service instance id like it is now. It is clearer, and it allows to avoid having to fetch the id again to delete the resource, or to read it (we can just use GET)

[Cocossoul]

I added a lot of comments, some I could have edited directly in your code but I did not find a way to edit directly the pull request without forking your fork and creating a PR on your fork. Do you know a better way ?

[sleungcy]

@Cocossoul let me take out the routeservice stuff from this PR

[sleungcy]

Since api v3 the route service binding ID was introduced. It is a breaking change but I think it would be best if the resource ID is the route service binding ID, and not the combination of route id and service instance id like it is now. It is clearer, and it allows to avoid having to fetch the id again to delete the resource, or to read it (we can just use GET)

Indeed. This will require implementing a stateupgrader, I'll have a look if you haven't got to it already

[sleungcy]

will be closing and recreating this

[sleungcy]

I added a lot of comments, some I could have edited directly in your code but I did not find a way to edit directly the pull request without forking your fork and creating a PR on your fork. Do you know a better way ?

Adding you as collaborator to my fork