DOC-768 Update http components

[asimms41]

Description

Resolves DOC-768
Review deadline: 26th February

Related PR to add these docs to the Cloud docs set: redpanda-data/cloud-docs#209

This pull request includes several updates to the modules/components/pages/inputs/http_client.adoc file, primarily focusing on improving clarity, consistency, and accuracy in the documentation. The most important changes include refining descriptions, adding optional indicators for certain fields, and reformatting for better readability.

Documentation Improvements:

• Simplified and clarified various descriptions, such as changing "Connects to a server and continuously performs requests for a single message" to "Connects to a server and continuously requests single messages."
• Added optional indicators for fields that do not have default values, such as oauth.consumer_key, oauth.consumer_secret, and others.
• Improved the explanation of dynamic URL and header settings and pagination, making it easier to understand how function interpolations can be used.
• Enhanced descriptions for OAuth and JWT authentication fields, providing clearer guidance on their usage. [1] [2]

Consistency and Formatting:

• Standardized terminology and formatting, such as changing "Common config fields, showing default values" to "Common configuration fields, showing default values."
• Reformatted examples and tips for better readability and consistency across the document. [1] [2]
• Ensured all field descriptions are concise and follow a consistent structure, such as "The URL to connect to. This field supports interpolation functions."

These changes collectively enhance the usability and accuracy of the documentation, making it easier for users to configure and understand the http_client component.

Page previews

Main page updates

• http_client input
• http_client output
• http processor

Updates for consistency

• websocket output
• websocket input
• schema_registry_decode processor
• schema_registry_encode processor

Checks

• New feature
• Content gap
• Support Follow-up
• Small fix (typos, links, copyedits, etc)

[netlify]

✅ Deploy Preview for redpanda-connect ready!

Name	Link
🔨 Latest commit	9188304
🔍 Latest deploy log	https://app.netlify.com/sites/redpanda-connect/deploys/67bc7995b345610008219287
😎 Deploy Preview	https://deploy-preview-176--redpanda-connect.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[asimms41]

Are you able to use the propagate_response or extract_headers fields in the Cloud? It looks like they both use http_server, and so should be hidden.

[mihaitodor]

You'd need an input which supports receiving these and I think http_server is the only one which does currently. If they don't use that input, they probably won't care about this feature.

[asimms41]

Does it make sense to condition these features out for Cloud users, i.e. this description, and the propagate_response, extract_headers fields? WDYT @mihaitodor and @Jeffail?

[Jeffail]

Sure, thats fine with me.

[mihaitodor]

LGTM, thank you!

[mihaitodor]

I don't have the context around these changes, but I wonder if the "no default" wording can get confusing, since an empty string ("") can be considered a default value. Connect shouldn't behave differently if, for example, dump_request_log_level: "" is present in the config or if it's omitted entirely.

[asimms41]

We have had feedback that users are not sure which are optional values and which are required. This is an attempt to resolve this. I could just change the labelling to Optional? WDYT @mihaitodor and @Jeffail?

[mihaitodor]

I could just change the labelling to Optional?

Sure, that makes sense to me

[mihaitodor]

You'd need an input which supports receiving these and I think http_server is the only one which does currently. If they don't use that input, they probably won't care about this feature.