Ingestion filtering should use OR logic for rules rather than AND

[aditya1702]

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

#5304

Why

We want transactions to be stored if it matches atleast one of the ingestion filtering rules.

Known limitations

[TODO or N/A]

[sreuland]

lgtm. left some comments on additional test coverage for consideration.

wanted to also suggest for consideration, would be worthwhile to add a changelog entry under Unreleased for this so that you can provide a more detailed description for it, as this is changing the inclusion behavior of filters and so, can highlight this as a 'breaking' change under Unreleased, otherwise the next release process would probably not pick up on this meaning, and it would just be added under general changes with the pr title.