SKIP UPDATE CHECK Refactoring BigBang chart to more closely mirror loki-simple-scalable from upstream

With all the updates and new 1.X based version of loki-simple-scalable it comes with features that the current BigBang chart tried to incorporate out-of-band like Grafana Enterprise Logs, Minio & centralized config ...configuration. Re-base the BigBang chart off of loki-simple-scalable version 1.7.6 and ensure that value transparency to Package CI, BB CI, and Production configurations are as transparent as possible.

Previous chart was based off 'single-binary' mode Loki : https://github.com/grafana/helm-charts/tree/main/charts/loki/ with changes to support 'loki-simple-scalable', Grafana Enterprise and objectStorage and secrets (which upstream for either did not support by default). Since the drop of version 1.X of 'loki-simple-scalable' it now has support for enterprise, objectStorage, templates for multiple configuration values, etc. The default for the chart was 'monolith' (single-binary mode) with BB enabling scalable, now the chart is set for the reverse: scalable is the default and if BB is set to monolith then single-binary is enabled and statefulset+templates for scalable are explicitly disabled.

Upgrades require deleting the previous logging-loki-read/write statefulsets as this overhaul changes port names, secrets, container names and many settings which will error out if not cleared out beforehand. This is configured to use previous chart minio buckets, or users will need to update their objectStorage.bucketNames value to persist data.

Relates https://repo1.dso.mil/platform-one/big-bang/bigbang/-/issues/1256