aws_lb_listener_rule: Add eventualy consistent read after creation

[gseyetik]

It is possible that during the creation of a elbv2 listener rule that the immediate read results in the newly created rule being removed from the state as it can not be found.

This adds a standard 1 minute time out for newly created resources.

Similar to #5167 .

Changes proposed in this pull request:

• Add a 1 minute eventual consistency read on creation of a elbv2 listener rule.

Output from acceptance testing:

None to run.

[bflad]

Looks great, thanks @gseyetik! 🚀

--- PASS: TestAccAWSLBListenerRule_multipleConditionThrowsError (1.27s)
--- PASS: TestAccAWSLBListenerRule_Action_Order (162.31s)
--- PASS: TestAccAWSLBListenerRule_oidc (189.36s)
--- PASS: TestAccAWSLBListenerRule_updateRulePriority (197.05s)
--- PASS: TestAccAWSLBListenerRule_redirect (201.16s)
--- PASS: TestAccAWSLBListenerRule_cognito (204.57s)
--- PASS: TestAccAWSLBListenerRule_changeListenerRuleArnForcesNew (210.52s)
--- PASS: TestAccAWSLBListenerRule_fixedResponse (214.53s)
--- PASS: TestAccAWSLBListenerRule_priority (234.31s)
--- PASS: TestAccAWSLBListenerRule_basic (265.98s)

[bflad]

This has been released in version 1.41.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!