fix(blooms): Remove backoff from notify planner

[salvacorts]

What this PR does / why we need it:
In #13306 we implemented a backoff mechanism to retry connecting to the builder. We added a backoff to connect to the builder to receive tasks, and another one to send back the results.

In this PR we remove the backoff to send back the result. I ran some experiments and:

• The context of the connection is not canceled when the connection to the planner is lost.
  • This is fine as the blocks and metas are pushed to the store and later planning cycles will take them into account.
• When the connection is broken to the planner, regardless of the backoff, it will always fail
• In (the unlikely) case that the planner is throttling CPU, gRPC already has some internal default retry mechanism for the Send and Receive operations.

We can revisit this if we decide to make the planner tolerant to restarts and make it able to pick it up where it failed.

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