ksonnet: generate tsdb_shipper storage_config even if using_boltdb_shipper is false

[Canuteson]

What this PR does / why we need it:
When configuring tsdb shipper without using bolt db shipper, the ksonnet library fails to generate the tsdb_shipper storage config.

Which issue(s) this PR fixes:
Fixes #11194

Special notes for your reviewer:

Checklist

• Reviewed the CONTRIBUTING.md guide (required)
• Documentation added
• Tests updated
• CHANGELOG.md updated
  • If the change is worth mentioning in the release notes, add add-to-release-notes label
• Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
• For Helm chart changes bump the Helm chart version in production/helm/loki/Chart.yaml and update production/helm/loki/CHANGELOG.md and production/helm/loki/README.md. Example PR
• If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory. Example PR

[CLAassistant]

All committers have signed the CLA.

[ashwanthgoli]

lgtm

[github-actions]

Trivy scan found the following vulnerabilities:

• HIGH openssl: Incorrect cipher key and IV length processing in libcrypto3 v3.1.2-r0. Fixed in v3.1.4-r0
• HIGH openssl: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow in libcrypto3 v3.1.2-r0. Fixed in v3.1.4-r1
• HIGH openssl: Incorrect cipher key and IV length processing in libssl3 v3.1.2-r0. Fixed in v3.1.4-r0
• HIGH openssl: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow in libssl3 v3.1.2-r0. Fixed in v3.1.4-r1