rename provider from cf to cloudfoundry

[gberche-orange]

This is a split of #38

To allow a tfstate to include both https://github.com/mevansam/terraform-provider-cf and https://github.com/orange-cloudfoundry/terraform-provider-cloudfoundry/ , the latter will be renamed to something like legacy_cloudfoundry, see orange-cloudfoundry/terraform-provider-cloudfoundry#33

[gberche-orange]

closed by #85

Migration steps for mevansam/terraform-provider-cf releases <= 0.9.8 are documented into #85 (comment)

[tgpo-sap]

@gberche-orange Following the links from your first post, the reason to rename cf_ to cloudfoundry_ is to address a comment from Terraform team, and this is more of aesthetic/styling/convention/standard purpose, not actually avoiding any functional code conflicts. May I know if my statement is correct? Thank you.

[gberche-orange]

@tgpo-sap yes you're right, hashicorp's request was to make the provider naming explicit and match naming conventions that aims to avoid ambiguous acronyms