Add acceptance test generator

[musa-cf]

Summary:

• add go.work files to gitignore list
• add test generation tool
• add some guides relevant to acceptance tests and tool usage

Tool usage examples

Happy path example:

> go run cmd/acctestgen/main.go new_service

To be created:
- file: internal/services/new_service/data_source_test.go
- file: internal/services/new_service/resource_test.go
- dir: internal/services/new_service/testdata/
- file: internal/services/new_service/testdata/resourcebasicconfig.tf
- file: internal/services/new_service/testdata/datasourcebasicconfig.tf

Do you confirm that the file paths above are correct? [y|n]: y

The files have been created. To run the acceptance tests, you will need to first
set the necessary environment variables. See https://github.com/cloudflare/terraform-provider-cloudflare/blob/v4.39.0/contributing/environment-variable-dictionary.md
for the list of variables. The values will vary depending on the account and zone being used for
the tests. Once the environment variables are set, you can run the tests using the command:

TF_ACC=1 go test ./internal/services/new_service -run "^TestAccCloudflare" -v -count 1s

With -dryrun flag:

> go run cmd/acctestgen/main.go -dryrun new_service

To be created:
- file: internal/services/new_service/data_source_test.go
- file: internal/services/new_service/resource_test.go
- dir: internal/services/new_service/testdata/
- file: internal/services/new_service/testdata/resourcebasicconfig.tf
- file: internal/services/new_service/testdata/datasourcebasicconfig.tf


Dry-run mode is enabled.

To create the files, run this again without the 'dryrun' flag

Example: go run cmd/acctest/main.go new_service

Error case:

go run cmd/acctestgen/main.go -dryrun fwaefawef

ERROR: service 'fwaefawef' not found

exit status 1

[jacobbednarz]

at a high level, i'm 👍 . two things we should do though to make the UX more consistent here are:

1. we move this into tools/ given we aren't expecting the consumer of the library to use this. it's internal only and should be stripped from the end package that terraform consumes. check out the current master version of this for some inspiration.
2. this should be wrapped in a scripts/... execution. the goal of the scripts directory is to have a unified interface with how we expose tooling to operators. a deeper read on this is at https://github.com/github/scripts-to-rule-them-all but in essence, it means we maintain this pattern for all of the repositories.

[musa-cf]

@jacobbednarz Thanks for the feedback! I've pushed a new commit with your suggestions.