Add support for tunnel_config

[Cyb3r-Jak3]

Adds support for tunnel configuration
Resolves #1756

Opening as a draft PR for early review while I fix ingress_rule not being configured.

[github-actions]

changelog detected ✅

[Cyb3r-Jak3]

The failing check is because I am using 127.0.0.1 as a tunnel ingress rule IP.

[jacobbednarz]

The failing check is because I am using 127.0.0.1 as a tunnel ingress rule IP.

instead of 127.0.0.1, can we use an internal (10.x/172.x) address instead that won't trigger the semgrep rules? if not, we can add a skip for this single file.

[Cyb3r-Jak3]

I've updated all the docs to use internal IPs addresses. The last reference is to the default IP for the proxy_address.

[jacobbednarz]

acceptance tests are all good

TF_ACC=1 go test $(go list ./...) -v -run "^TestAccCloudflareTunnelConfig_" -count 1 -parallel 1 -timeout 120m -parallel 1
?   	github.com/cloudflare/terraform-provider-cloudflare	[no test files]
=== RUN   TestAccCloudflareTunnelConfig_Full
--- PASS: TestAccCloudflareTunnelConfig_Full (15.76s)
=== RUN   TestAccCloudflareTunnelConfig_Short
--- PASS: TestAccCloudflareTunnelConfig_Short (16.80s)
PASS
ok  	github.com/cloudflare/terraform-provider-cloudflare/internal/provider	32.919s

[jacobbednarz]

nice one @Cyb3r-Jak3 🏆

[github-actions]

This functionality has been released in v3.29.0 of the Terraform Cloudflare Provider.

Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!