SUP-1068 Migrate pipeline resource to framework

[jradtilbrook]

PR checklist:

• docs/ updated
• tests added
• an example added to examples/ (useful to demo new field/resource)
• CHANGELOG.md updated with pending release information

Theres a few things I want to test manually

• changing cluster from empty string to null
• provider_settings is technically a list block but we shouldn't allow that. what happens if its just changed under the hood
• ... TBD

[jradtilbrook]

The resource now sets this as null instead of an empty string

[james2791]

Noting testAccPipelineConfigBasicWithTeam("foo") clears the cluster ID off the pipeline - and new impl sets it as null - this LG

[jradtilbrook]

Alright I think this is ready for review again. With framework, when defining a block attribute you cannot set it as required or a default value. And the framework also performs validation on the state. This causes trouble for the provider_settings block. It is optional which means that the provider cannot set any values into state if the user has not defined it. The SDKv2 version of the provider would still perform some actions using default values which is not possible now. And I cannot find a way around it.

I think long-term, moving to protocol v6 and converting it to a nested attribute is the way to go

[mcncl]

@jradtilbrook I think maybe we let Pagerduty know they need to look at updating sooner rather than later?

[jradtilbrook]

@jradtilbrook I think maybe we let Pagerduty know they need to look at updating sooner rather than later?

@mcncl yeah I think so. The good news is that the latest release has basically all the new features we were aiming for for v1. Its just some bug fixes from here. So if they can pin their version now, they won't really miss out on anything (especially if they haven't hit the cases for the bugs)

[james2791]

I think this is at a point of rolling-in, LGTM 👍