fix(mixins): add backend path section in loki-operational for single scalable deployment

[QuentinBisson]

What this PR does / why we need it:

This PR adds a backend path row in loki operational just after the read path

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Checklist

• Reviewed the CONTRIBUTING.md guide (required)
• Documentation added
• Tests updated
• Title matches the required conventional commits format, see here
  • Note that Promtail is considered to be feature complete, and future development for logs collection will be in Grafana Alloy. As such, feat PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.
• 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

[cstyan]

sorry for the delay @QuentinBisson, I was away last week, can review this week

[QuentinBisson]

@cstyan don't worry about it, I was busy fixing Mimir mixins 😅

Now regarding this one, i was wondering if it would not be better to have a single single scalable resource dashboard instead of having 1 for read, 1 for write and 1 for backend that all contain only 1 row anyway. What do you think?

[cstyan]

@cstyan don't worry about it, I was busy fixing Mimir mixins 😅

Now regarding this one, i was wondering if it would not be better to have a single single scalable resource dashboard instead of having 1 for read, 1 for write and 1 for backend that all contain only 1 row anyway. What do you think?

that seems like a good idea to me 👍

[QuentinBisson]

PR is here #13471

[QuentinBisson]

@cstyan I renamed the PR to match what it really does as the Merge PR for resources is here #13471

[QuentinBisson]

@cstyan would you be able to review my PRs?

[cstyan]

@QuentinBisson again, need to merge in main after the other PRs were merged

[cstyan]

did you mean to change this, or was it a linter change?

[QuentinBisson]

I did, I thought having both read dashboards close to each other made sense but I can revert this one of you prefer