services/horizon: Skip state verification on GetExpStateInvalid error

[bartekn]

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

Return from maybeVerifyState when GetExpStateInvalid returns an error.

Why

stateInvalid may be incorrect in such case.

Known limitations

[TODO or N/A]

[sreuland]

do you think there's any worthwhile change on coverage in the unit test that hits this method to assert this outcome, I was looking at https://github.com/bartekn/go/blob/skip-state-verify-when-error/services/horizon/internal/ingest/main_test.go#L183

[bartekn]

@sreuland good call! I improved the test in 4a9f86d.