doc: Close code block in "Resource: Cloud Provider Access Configuration Paths" documentation page

[mattt416]

Description

The Resource: Cloud Provider Access Configuration Paths documentation page currently does not render correctly due to missing closing code block.

Link to any related issue(s):

Type of change:

• Bug fix (non-breaking change which fixes an issue). Please, add the "bug" label to the PR.
• New feature (non-breaking change which adds functionality). Please, add the "enhancement" label to the PR.
• Breaking change (fix or feature that would cause existing functionality to not work as expected). Please, add the "breaking change" label to the PR.
• This change requires a documentation update
• Documentation fix/enhancement

Required Checklist:

• I have signed the MongoDB CLA
• I have read the contribution guidelines
• I have added tests that prove my fix is effective or that my feature works per HashiCorp requirements
• I have added any necessary documentation (if appropriate)
• I have run make fmt and formatted my code
• If changes include deprecations or removals, I defined an isolated PR with a relevant title as it will be used in the auto-generated changelog.

Further comments

[jwilliams-mongo]

@Zuhairahmed LGTM. One other formatting issue I see is on line 64 there seems to be an extra "" after provider_name` (can't comment there on the PR)

at a glance all the other formatting looks OK

[mattt416]

@jwilliams-mongo Just added another commit for that. Thanks for catching!

[jwilliams-mongo]

@mattt416 LGTM

[github-actions]

This PR has gone 7 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 7 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!

[mattt416]

@jwilliams-mongo @maastha is this PR waiting on something from me?

[jwilliams-mongo]

@mattt416 LGTM from here. I think it just needs to be merged. I don't have write access, so it will have to be @maastha or someone else from the engineering team.