protocols/horizon: Apply deprecation on some operation types, updating them to the correct value

[abuiles]

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

Update type name for operations: pathPaymentStrictReceive, manageSellOffer, and createPassiveSellOffer. Fixes #2132

Why

The used type doesn't match the operation type, we delayed this change up to 0.25.0 and we are doing it now.

Known limitations

[TODO or N/A]

[abuiles]

This is branched off from int64-string -- I have that as the base for now since there are overlapping changes. I'll update it once we merge int64-string into the release branch.

[abuiles]

sorry, I merge this into the int64 branch, undoing it and waiting until we merge that one in the release branch.