Migrate provider from cloudfoundry-community to cloudfoundry

[rahearn]

🎫 Addresses issue: #56

closes #56

🛠 Summary of changes

• updates all resources to use the new cloudfoundry/cloudfoundry provider except clamav and egress_proxy both still have references to the community provider to use cloudfoundry_network_policy
• lots of breaking changes with input variables, getting rid of unneeded cf_org_name and changing from cf_space_name to cf_space_id or cf_space (entire space resource) to help terraform properly sequence creation
• I had issues trying to mock out cloudfoundry_service_plans data so I switched to using more real provider in tests and less mocking, and using override_resource to prevent creating expensive infrastructure
• There is not currently an upgrade path for apps using the existing v1.x modules. I plan on adding an UPGRADING.md file with tips, but I also think most apps will stick on the version they started with for the most part.

📜 Testing Plan

While this is in draft, I used it in a new application to verify behavior, and attempt to update an existing app to generate content for the UPGRADING doc.

It's been used for both GSA-TTS/continuous-assessment-poc#66 and GSA-TTS/gitlab-runner-cloudgov#62

[mogul]

Most of these are optional, but I think the service-plan indexing ones are important.

[mogul]

Most of these are optional, but I think the service-plan indexing ones are important.

OK, turns out those were not important because cloudfoundry_service_plans filters the results; I understand that now and resolved those.

[mogul]

🚢🐿️