services/horizon: Use percentile_disc in fee stats query

[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.

When looking at the Dashboard I realized that when there are a lot of transactions with normal fees and one tx with a much bigger fee the p99 can be interpolated to a huge number. See:

I checked the last few ledgers at the moment of the screenshot and no transaction had such a big fee.

This commit fixes fee stats query to use Postgres' percentile_disc instead of percentile_cont.

[leighmcculloch]

Makes sense to me to use the discreet value at each percentile rather than interpolating. One question below.

[abuiles]

👍