ingest/ledgerbackend: Remove captive core info request error logs

[tamirms]

PR Checklist

PR Structure

• This PR has reasonably narrow scope (if not, break it down into smaller PRs).
• This PR avoids mixing refactoring changes with feature changes (split into two PRs
  otherwise).
• This PR's title starts with name of package that is most changed in the PR, ex.
  services/friendbot, or all or doc if the changes are broad or impact many
  packages.

Thoroughness

• This PR adds tests for the most critical parts of the new functionality or fixes.
• I've updated any docs (developer docs, .md
  files, etc... affected by this change). Take a look in the docs folder for a given service,
  like this one.

Release planning

• I've updated the relevant CHANGELOG (here for Horizon) if
  needed with deprecations, added features, breaking changes, and DB schema changes.
• I've decided if this PR requires a new major/minor version according to
  semver, or if it's mainly a patch change. The PR is targeted at the next
  release branch if it's not a patch change.

What

Captive core configures two prometheus metrics which periodically probe the info http endpoint on captive core. If the info request fails, we currently log the error.

Why

This commit removes the logs because we are already probing the info http endpoint and logging errors in https://github.com/stellar/go/blame/master/services/horizon/internal/app.go#L401C15-L401C36 . Therefore the logs here are redundant. Also, in #4894 and #5108 we added logic to suppress error logs during the build state, and if we keep this logging code we will have to reimplement this logic again.

Known limitations

[N/A]