KV: add bulk gets documentation

[teresalves]

Summary

Screenshots (optional)

Documentation checklist

• The documentation style guide has been adhered to.
• If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
• Files which have changed name or location have been allocated redirects.

[hyperlint-ai]

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.

---

PR Change Summary

Enhanced KV documentation to include bulk retrieval of key-value pairs.

• Updated the get() method documentation to support multiple keys retrieval.
• Added examples for fetching multiple keys and their responses.
• Introduced getWithMetadata() method for retrieving values with associated metadata.

Modified Files

• src/content/docs/kv/api/read-key-value-pairs.mdx

---

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

[Oxyjun]

Is this an intentional change? I don't actually know what this does.

[teresalves]

This was me, I was having some issues rendering the mdx files locally. Reverted it :)

[thomasgauvin]

There is not enough size difference between #### and ##### @Oxyjun @KianNH. Any chance we can increase the font size for ####?

[Oxyjun]

There is not enough size difference between #### and ##### @Oxyjun @KianNH. Any chance we can increase the font size for ####?

You're right that the size difference isn't big between H4 and H5. I can raise this for discussion within the team :D

FYI, as a general rule of thumb, we want to avoid H4s and lower - at that level of granularity of headings, users might not find the heading hierarchy very useful. If you have a single page which warrants H5s, I would recommend creating a new chapter it?

[Oxyjun]

Incomplete sentence FYI @thomasgauvin