feat(tekton provider): Update tekton provider

[briangleeson]

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Changes

Update the tekton pipeline provider with latest go sdk:

• Bump github.com/IBM/continuous-delivery-go-sdk to v0.0.8
• Refactor naming scheme from tekton_pipeline_* to cd_tekton_pipeline_*
• Add some new diff suppress functions
• Add ForceNew to a few schemas where necessary for immutable values
• Add enum handling to Trigger Property
• Add missing description for some id properties
• Added href property to pipeline run resource
• Update all strings after internal review
• Change created property to created_at
• Breaking: Change concurrency object property to max_concurrent_runs integer property
• Add support for the preview worker option in v2 APIs, when supported in that region. Falls back to public if not supported
• Breaking: Reshape scm source object to include service_instance_id
• Change patch requests to use JSON merge-patch content-type
• Rename html_url to runs_url and run_url, for pipeline and pipelineRun resources respectively
• Breaking: Reshape property types to use snake case: text, single_select, integration, secure, appconfig
• Breaking: Reshape secret types to use snake case: token_matches, digest_matches, internal_validation
• Add support for enable_slack_notifications and enable_partial_cloning pipeline settings
• Breaking: Reshape enum value to remove the default option in favour of value instead
• Breaking: Refactored Trigger into separate request and response shapes

Output from acceptance testing:

$ make testacc TEST=./ibm/service/cdtoolchain TESTARGS='-run=TestAccIBMCdToolchain*'

=== RUN   TestAccIBMCdToolchainDataSourceBasic
--- PASS: TestAccIBMCdToolchainDataSourceBasic (52.43s)
=== RUN   TestAccIBMCdToolchainDataSourceAllArgs
--- PASS: TestAccIBMCdToolchainDataSourceAllArgs (46.79s)
=== RUN   TestAccIBMCdToolchainToolAppconfigDataSourceBasic
--- PASS: TestAccIBMCdToolchainToolAppconfigDataSourceBasic (49.96s)
=== RUN   TestAccIBMCdToolchainToolAppconfigDataSourceAllArgs
--- PASS: TestAccIBMCdToolchainToolAppconfigDataSourceAllArgs (48.36s)
=== RUN   TestAccIBMCdToolchainToolArtifactoryDataSourceBasic
--- PASS: TestAccIBMCdToolchainToolArtifactoryDataSourceBasic (75.43s)
=== RUN   TestAccIBMCdToolchainToolArtifactoryDataSourceAllArgs
--- PASS: TestAccIBMCdToolchainToolArtifactoryDataSourceAllArgs (56.61s)
=== RUN   TestAccIBMCdToolchainBasic
--- PASS: TestAccIBMCdToolchainBasic (85.75s)
=== RUN   TestAccIBMCdToolchainAllArgs
--- PASS: TestAccIBMCdToolchainAllArgs (71.86s)
=== RUN   TestAccIBMCdToolchainToolPipelineBasic
--- PASS: TestAccIBMCdToolchainToolPipelineBasic (48.86s)
=== RUN   TestAccIBMCdToolchainToolPipelineAllArgs
--- PASS: TestAccIBMCdToolchainToolPipelineAllArgs (91.56s)
PASS
ok      github.com/IBM-Cloud/terraform-provider-ibm/ibm/service/cdtoolchain     633.398s

$ make testacc TEST=./ibm/service/cdtektonpipeline TESTARGS='-run=TestAccIBMCdTekton*'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./ibm/service/cdtektonpipeline -v -run=TestAccIBMCdTekton* -timeout 700m
=== RUN   TestAccIBMCdTektonPipelineBasic
--- PASS: TestAccIBMCdTektonPipelineBasic (99.81s)
PASS
ok      github.com/IBM-Cloud/terraform-provider-ibm/ibm/service/cdtektonpipeline        105.269s

Remaining work

• Update the GO sdk version used for tekton pipeline once the new version has been published
• Fix the detect-secrets errors in PR build
• Fix cdtektonpipeline tests

[briangleeson]

Moving this back to draft for now. We have more changes identified that we'd like to add to this before moving forward

[briangleeson]

• Large amount of String updates added
• Refactored created, updated and concurrency properties
• Added href property to pipeline run resource
• Updated docs

[briangleeson]

TODO

• resolve merge conflicts
• update GO sdk version once built and available

[briangleeson]

@hkantare we are close to completing this piece of work. I'm wondering about the process to get this change (once approved) out into a provider release. Can you point me to a doc that describes this process?

[briangleeson]

TODO: update continuous-delivery-go-sdk version once the new build is available

[briangleeson]

@hkantare I've marked the PR ready for review again. Let me know if you have any feedback, thanks