Add new captive core flags to ledgerbackend toml

[chowbao]

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 new captive core toml options EMIT_SOROBAN_TRANSACTION_META_EXT_V1 and EMIT_LEDGER_CLOSE_META_EXT_V1

Why

These flags are used to emit more detailed Soroban fee information as defined here

[leighmcculloch]

👍🏻

Going to take the opportunity to promote this issue that I think we should do address, and if addressed would eliminate the need for these updates:

• ingest: use of strict captive-core config makes horizon/soroban-rpc unnecessarily incompatible with new stellar-core features #5027

cc @mollykarcher