Log peering wait errors, use ReadTimeout in peering Data Sources

[jjti]

🛠️ Description

Occasionally we get what look like timeouts while waiting on Azure peerings to flip to ACTIVE:

TestE2E_BasicAzure 2022-07-29T17:56:40Z logger.go:66: module.hcp_peering.data.hcp_azure_peering_connection.peering: Still reading... [19m50s elapsed]
TestE2E_BasicAzure 2022-07-29T17:56:50Z logger.go:66: 
TestE2E_BasicAzure 2022-07-29T17:56:50Z logger.go:66: Error: error waiting for peering connection (azure-e2e-68625cad-peer) to become 'ACTIVE'
TestE2E_BasicAzure 2022-07-29T17:56:50Z logger.go:66: 
TestE2E_BasicAzure 2022-07-29T17:56:50Z logger.go:66:   with module.hcp_peering.data.hcp_azure_peering_connection.peering,
TestE2E_BasicAzure 2022-07-29T17:56:50Z logger.go:66:   on .terraform/modules/hcp_peering/main.tf line 117, in data "hcp_azure_peering_connection" "peering":
TestE2E_BasicAzure 2022-07-29T17:56:50Z logger.go:66:  117: data "hcp_azure_peering_connection" "peering" {
TestE2E_BasicAzure 2022-07-29T17:56:50Z logger.go:66: 
TestE2E_BasicAzure 2022-07-29T17:56:50Z retry.go:99: Returning due to fatal error: FatalError{Underlying: error while running command: exit status 1; 
Error: error waiting for peering connection (azure-e2e-68625cad-peer) to become 'ACTIVE'

  with module.hcp_peering.data.hcp_azure_peering_connection.peering,
  on .terraform/modules/hcp_peering/main.tf line 117, in data "hcp_azure_peering_connection" "peering":
 117: data "hcp_azure_peering_connection" "peering" {
}

This repeatedly happens right at 20 minutes, which is the default timeout. That doesn't make a lot of sense, be we ourselves set the Timeout to 35 minutes in multiple places. The changes in this PR are to 1. try to log failures seen waiting on the peering state transition and 2. set the Read timeout to 35 minutes explicitly (vs using just Timeouts.Default).

🚢 Release Note

Release note for CHANGELOG:

* data_source_azure_peering_connection: log failed peering wait errors [GH-363]

🏗️ Acceptance tests

• Are there any feature flags that are required to use this functionality?
• Have you added an acceptance test for the functionality being added?
• Have you run the acceptance tests on this branch?

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccXXX'

...