services/horizon/internal: Deprecate captive-core-config-append-path

[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

Deprecate --captive-core-config-append-path in favor of --captive-core-config-path. The difference between the two is that when --captive-core-config-path is used Horizon will validate the configuration file to reject any fields which are not supported by captive core.

Close #3442

[ire-and-curses]

@paulbellamy Let's make sure we clearly identify this deprecation in the changelog and release notes. I know it's not breaking but we should tell people.