operator: Include runtime-config in compiling the SHA1 checksum

[btaani]

What this PR does / why we need it:
Any changes made to the runtime-config can now trigger the reconciliation of the LokiStack.

Which issue(s) this PR fixes:
Fixes:
LOG-3953 - Updating the RulerConfig CR can now trigger the restart of the ruler pod (and thus reflecting the changes to the user-workload AM)
LOG-3950 - Enabling user-workload AM

Special notes for your reviewer:

Checklist

• Reviewed the CONTRIBUTING.md guide (required)
• Documentation added
• Tests updated
• CHANGELOG.md updated
• Changes that require user attention or interaction to upgrade are documented in docs/sources/upgrading/_index.md

[periklis]

The proposed change set works against our first principles that the operator should delegate anything possible to the Kubernetes APIServer instead of inventing the wheel anew.

By saying this, I suggest you take a look on the code path starting from this snippet to discover how we instruct k8s to restart pods by passing annotations to the pod template spec:

loki/operator/internal/handlers/lokistack_create_or_update.go

Lines 267 to 270 in 11f5218

	certRotationRequiredAt := ""
	if stack.Annotations != nil {
	certRotationRequiredAt = stack.Annotations[manifests.AnnotationCertRotationRequiredAt]
	}

I.e. The ruler config annotation is something that is updated on the LokiStack CR on every RulerConfig change. Affected components, e.g. ruler needs this annotation to be passed to the pod template spec.

[btaani]

@periklis updating the annotations is already implemented here for RulerConfig changes. However, updating anything below the overrides section of the RulerConfig CR updates the annotationRulerConfigDiscoveredAt value for the lokistack, but doesn't seem to trigger restarting the ruler pod, which is why I explicitly restart it like this.
I do understand your argument though. I'll redo it to match the rest of our operator code

[periklis]

Do we need this change?