feat(logcli): add --log.level parameter

[bboreham]

What this PR does / why we need it:

To help with diagnosing errors when using logcli.

Which issue(s) this PR fixes:
N/A

Special notes for your reviewer:
It feels a little ugly to pull in dskit references in a command-line program. Open to any suggestions of other ways to do it.

Also I'm not sure if the default setting of error will log anything new that users don't want to see.

Checklist

• Reviewed the CONTRIBUTING.md guide (required)
• Documentation added
• NA 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.
• NA Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
• NA 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

[github-actions]

💻 Deploy preview deleted.

[bboreham]

Error: No release type found in pull request title "feat [logcli]: add --log.level parameter". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

I did read that page and tried to follow its advice. Are scopes not allowed?

[slim-bean]

I guess the syntax is a bit different, feat(logcli) vs feat[logcli]

[bboreham]

Thanks, I now see the confusion. In the summary <type>[optional scope]: <description>, the square brackets are meta-syntax.
The real specification says "4. A scope MUST consist of a noun describing a section of the codebase surrounded by parenthesis, e.g., fix(parser):"