docs: full copy-edit of webHDFS page

[agilgur5]

Motivation

Am making a few larger copy-edits now that I'm (very) familiar with the docs; this was one of the smaller ones that I managed to complete. This page is particularly self-encompassing, so works well as a first. It's also a great example page but had a bit of verbosity to it -- it's now considerably more concise.

• Follow-up to docs: fix typos and simplify wording on SSO page #11341 et al where I first mentioned doing larger copy-edits, but did not do at the time

Primarily in order to follow the k8s docs style guide and simplify docs to make them more approachable to all audiences

Modifications

Stylistic changes

• use more direct language, per k8s style guide

  • "Using webHDFS protocol via HTTP artifacts" -> "webHDFS via HTTP artifacts"
  • "In order to use [...] we will make use of" -> "You can use"
  • "HTTP URL" -> "URL"
    • also consistently use the term "query paramter" instead of "HTTP URL parameter", which is ambiguous (path params, query params, etc)
  • "need to append" -> "append"
  • "This results in the following URL" -> "The result is"
  • "Now, when run, the workflow will" -> "The workflow will"
  • "There are some additional fields that can be set" -> "Additional fields can be set"
  • "In order to declare" -> "To delcare"
  • "need to change [...] to" -> "instead use"
  • "where we want the [...] to be stored" -> "your desired location"
  • "want to store the artifact under" -> "artifact will be stored at"
  • "also supply the optional overwrite [...] to allow [...]" -> "can overwrite [...] with"
  • "may want to provide some authentication option" -> "may want to use authentication"
  • "a usage of [...] can be realized by supplying" -> "can be used via"
  • several other more complex / multi-sentence simplifications

• use in-line links, per k8s style guide

• consistently use "the full webHDFS example" when referring to the main example (instead of differing descriptions for the same example)

• remove "all you need", "little change", "only", etc per k8s style guide

• address the reader as "you", per k8s style guide

• replace Latin phrases, per k8s style guide

• move "Additional fields" sentence to after the in-line example, as the example does not use those and it is a side note

• comment out elipses in code blocks so that they are more copyable / valid syntax

• use an infobox instead of "Limitation:" to be consistent with the rest of the docs

• minor grammatical fixes

  • extra commas, extra articles, etc

Semantic changes

• add links to HTTP artifacts and the overwrite parameter
  • remove note about overwrite depending on provider. the (newly linked) docs specify that it defaults to false
• clarify the difference between Hadoop native auth and provider dependent auth
  • specify that tokens are used via the delegation query param, per the linked docs

Verification

Checked that all new links work, page renders.

Future Work

1. This page really doesn't fit under "Use Cases", which is intended for broad proposes, such as "Machine Learning", not a very specific example. This might fit better under "Patterns".
   • I was going to just move it, but it will require a redirect as its URL is currently under use-cases/.
     • and redirects are not built into mkdocs, they require a plugin, so that requires an extra dep and configuration etc
       • redirects are good to have in general though, so I will probably add this in a separate PR