Add Consecutive_up and Consecutive_down for load_balancer_monitor res…

[Nmishin]

Description

We can set the consecutive_down and consecutive_up parameter values for the Cloudflare Load Balancer Monitor via API but not via terraform.

Issue from terraform-provider-cloudflare

Has your change been tested?

Yes, relevant unit tests have been updated to handle the addition of this field. Additionally, changes were ran against the pre-existing test suite to verify that no regressions were introduced.

Types of changes

What sort of change does your code introduce/modify?

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• This change is using publicly documented in cloudflare/api-schemas
  and relies on stable APIs.

[github-actions]

changelog detected ✅

[codecov-commenter]

Codecov Report

Merging #1380 (7bdb342) into master (b9ac804) will increase coverage by 0.00%.
Report is 203 commits behind head on master.
The diff coverage is 49.62%.

@@           Coverage Diff            @@
##           master    #1380    +/-   ##
========================================
  Coverage   48.33%   48.34%            
========================================
  Files         133      139     +6     
  Lines       13023    13749   +726     
========================================
+ Hits         6295     6647   +352     
- Misses       5201     5453   +252     
- Partials     1527     1649   +122     

Files Changed	Coverage Δ
access_audit_log.go	79.31% <ø> (ø)
access_bookmark.go	72.44% <ø> (ø)
access_keys.go	71.42% <ø> (ø)
access_organization.go	53.84% <ø> (ø)
access_service_tokens.go	51.85% <ø> (ø)
account_members.go	65.54% <ø> (ø)
account_roles.go	53.84% <ø> (ø)
accounts.go	50.81% <ø> (ø)
addressing_address_map.go	39.04% <ø> (ø)
addressing_ip_prefix.go	45.45% <ø> (ø)
... and 121 more

... and 1 file with indirect coverage changes

[jacobbednarz]

thanks for the PR. looks good overall but we should use camel casing for the struct names.

[jacobbednarz]

cc @gofish @tc80

[github-actions]

This functionality has been released in v0.76.0.

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