Docs: Refactor /usage/responses into a divided section

[JacobCoffee]

Summary

What

After reading through it this is quite a long page, even with adding to dropdowns.

rfc @litestar-org/maintainers, open to not doing this too - but as someone who just read through it it was tough.

How

• https://docs.litestar.dev/latest/usage/responses.html
• https://github.com/litestar-org/litestar/blob/a0522413474ca83d4c99fda2fd0a548467302785/docs/usage/responses.rst

Split this section up into something like

responses/
├── index.rst
├── media_types_and_status_codes.rst
├── returning_responses.rst
├── headers_and_cookies.rst
├── special_responses.rst
└── advanced_topics.rst

index.rst contents

• Introductory section
• Overview of other sections
• What is current under the Responses section.

media_types_and_status_codes.rst contents

• Media Types section
• Status Codes section

returning_responses.rst contents

• JSON Responses
• MessagePack Responses
• Plaintext responses
• HTML responses
• Content Negotiation
• Redirect Responses

headers_and_cookies.rst contents

• Setting Response Headers section
• Setting Headers Dynamically
• Using Annotated Responses
• Using the After Request Hook
• Predefined Headers
• Cache Control
• ETag
• Setting Response Cookies
• Setting Cookies dynamically
• Using Annotated Responses
• Using the After Request Hook

special_responses.rst contents

(idk about this, maybe should just go into the return_responses.rst

• File Responses
• Streaming Responses
• Server Sent Event Responses
• Template Responses
• Custom Responses

advanced_topics.rstcontents

• Background Tasks
• Executing Multiple Background Tasks
• Pagination
• Classic Pagination
• Offset Pagination
• Offset Pagination With SQLAlchemy <https://www.sqlalchemy.org/>_
• Cursor Pagination

---

Note

While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.

Check out all issues funded or available for funding on our Polar.sh dashboard

• If you would like to see an issue prioritized, make a pledge towards it!
• We receive the pledge once the issue is completed & verified
• This, along with engagement in the community, helps us know which features are a priority to our users.

[peterschutt]

I think this would be a nice improvement. Also, DYT we should bring the responses menu item up to the top underneath requests?

[provinzkraut]

I have already started to work on this (and related things) in #2912.