Add --console flag for captive core 19.3.0

[paulbellamy]

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

Add --console flag for captive core 19.3.0

Why

So that logs still show up intermingled with the horizon log output, after the core 19.3.0 breaking change.

Known limitations

• Core logs will no longer show up in their own separate place. e.g. var/lib/stellar.

• Will break this version of horizon with core < 19.3.0

• depends on bump core to latest 19.3.0 #4485

[bartekn]

LGTM! Please update CHANGELOG in breaking changes section.