[fix] logging docu: splunk config and indentation of example code

[papanito]

The splunk configuration was wrong as splunkHec starts with lower s.
Also fields are hec_host and hec_port.

When contributing to docs, please don't update the content in the v2.x folder.
It's better to update the versioned docs, for example, the v2.5 or v2.6 docs.

This content in v2.x was separated into versioned documentation during the v2.5.8
release. The content relevant to Rancher versions before v2.5 went into the v2.0-v2.4
folder, while the content related to Rancher v2.5 went into the v2.5 folder.

We are trying to get the 2.x content to be removed from Google search results. The only
reason we haven't deleted it is because Google search results would lead to 404
errors if we deleted it.

[ansilh]

The doc on the banzai side is autogenerated vi acode and looks like the mistake started from there.

[ansilh]

Let's merge this PR and keep Rancher docs accurate.
Sure, you can submit a PR in logging operator upstream too.

[papanito]

Yeah I also fixed it upstream:

• https://github.com/banzaicloud/logging-operator-docs/pull/80
• [fix] Fields hec_host and hec_port in splunk example kube-logging/logging-operator#805

[ansilh]

Thanks @papanito
Was there any reason not to change splunkHec (starting with small "s" instead of caps) in the upstream?

[papanito]

Nope I guess I missed that. Will fix it...

[papanito]

@catherineluse anything missing?
Btw. I assume now that you have 2.6 docu it should also go there?

[catherineluse]

@papanito Yes, if it's valid for Rancher 2.6 it should go in the 2.6 directory.

[papanito]

I will create a separate PR for 2.6.x but I guess would not hurt to also update 2.5.x docu ;-)

[btat]

Merging and will use https://github.com/rancher/docs/issues/3520 for tracking of the 2.6 port

[papanito]

Thanks @btat