Add support for email routing

[Cyb3r-Jak3]

Resolves #1460

Adds terraform support for Email Routing.

[github-actions]

changelog detected ✅

[Cyb3r-Jak3]

Tests pass when using cloudflare/cloudflare-go#1070

$ TESTARGS='-run "TestAccTestEmailRouting" -count 1 -parallel 1' make testacc
TF_ACC=1 go test $(go list ./...) -v -run "TestAccTestEmailRouting" -count 1 -parallel 1 -timeout 120m -parallel 1
?       github.com/cloudflare/terraform-provider-cloudflare     [no test files]
=== RUN   TestAccTestEmailRoutingAddress
--- PASS: TestAccTestEmailRoutingAddress (2.98s)
=== RUN   TestAccTestEmailRoutingCatchAll
--- PASS: TestAccTestEmailRoutingCatchAll (2.23s)
=== RUN   TestAccTestEmailRoutingRule
--- PASS: TestAccTestEmailRoutingRule (2.19s)
=== RUN   TestAccTestEmailRoutingSettings
--- PASS: TestAccTestEmailRoutingSettings (2.20s)
PASS
ok      github.com/cloudflare/terraform-provider-cloudflare/internal/provider   9.610s
?       github.com/cloudflare/terraform-provider-cloudflare/tools/cmd/changelog-check   [no test files]
?       github.com/cloudflare/terraform-provider-cloudflare/tools/cmd/maintainer-only-file-check        [no test files]
?       github.com/cloudflare/terraform-provider-cloudflare/tools/cmd/tf-log-check      [no test files]
?       github.com/cloudflare/terraform-provider-cloudflare/version     [no test files]

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
-	Generic High Entropy Secret	421cb7b	examples/resources/cloudflare_pages_project/resource.tf	View secret
-	Generic High Entropy Secret	421cb7b	internal/provider/resource_cloudflare_pages_project_test.go	View secret
-	Generic High Entropy Secret	421cb7b	internal/provider/resource_cloudflare_pages_project_test.go	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[github-actions]

This functionality has been released in v3.23.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!