Improve transport configuration docs

[dolfinus]

• Options of Java transport have duplicated description for Spark & Flink, and had no description for Yaml. Moved transport description to a common section.
• Update both Java and Python transport config description to match each other. Configuration options, behavior, examples and notes are described in separated sections. Option names are monospaced.
• Improve Spark & Flink examples to show all the described options. Including type which was missing before.
• Add Java & Python code examples for each transport type, not just for HTTP.

[netlify[bot]]

✅ Deploy Preview for mellifluous-eclair-326dcd ready!

Name	Link
🔨 Latest commit	ef10d234e7940f2c4e2200ca3b3c610e61649bbd
🔍 Latest deploy log	https://app.netlify.com/sites/mellifluous-eclair-326dcd/deploys/6620ed07912bb20008ad195b
😎 Deploy Preview	https://deploy-preview-319--mellifluous-eclair-326dcd.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.

[dolfinus]

Regarding Java & Python code examples for each transport - this is probably should be moved somethere to javadoc/docstrings, to keep examples close to the code

[kacpermuda]

Regarding Java & Python code examples for each transport - this is probably should be moved somethere to javadoc/docstrings, to keep examples close to the code

IMHO we should not remove them from the docs, but we can always add a doc reference in the docstrings, so the users can quickly see the examples. We could copy those examples, but then keeping them in sync can be a pain.