kubo rpc: tls and basic http auth guide

[2color]

What's in this PR

Add guide on how to set up Caddy for TLS termination and basic http auth in Kubo.

Checklist before merging

• Link to this guide in

  ipfs-docs/tools/http-api-docs/markdown.go

  Lines 79 to 86 in 6cb430e

  	::: danger NEVER EXPOSE THE RPC API TO THE PUBLIC INTERNET
  	The RPC API provides admin-level access to your Kubo IPFS node, including `+"`/api/v0/config`"+`.
  	It is bound to `+"`localhost`"+` by default on purpose. You should never expose it to the public internet, just like you would never expose a SQL database or other backend service.
  	If you are looking for an interface designed for browsers and public internet, consider implementation-agnostic [HTTP Gateway](../../reference/http/gateway.md) instead.
  	:::

• Passing all required checks (The beta Check Markdown links for modified files check is not required)

[lidel]

thanks, lgtm, pushed small cosmetics, and tested API generator, both look fine.
optional suggestions below but also ok to merge as-is