fix(canary): Reconnect immediately upon tail max duration

[emadolsky]

What this PR does / why we need it:
Canary latency metrics report high latency every hour as a result of tail_max_duration configuration. As it is possible for canary to recognise this special case, and since there is no need to go through the regular behaviour of sleeping for 10 seconds (which causes the high latency reported), it makes sense to reconnect immediately.

Which issue(s) this PR fixes:
It is related to #5086 but doesn't fix the original issue stated there.
This PR aims to improve the metrics reported by canary.

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

[CLAassistant]

All committers have signed the CLA.

[MasslessParticle]

@emadolsky Thanks for contributing! It looks like there's some linting that needs to be fixed before we can merge

[emadolsky]

Hey @MasslessParticle Can I get approval for the workflows?

[MasslessParticle]

Thanks again!