Parse LIMIT_TX_QUEUE_SOURCE_ACCOUNT in core config

[mollykarcher]

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

Porting this change #4882 from soroban-xdr-next into master.

Why

Core wants to be able to release the 1 transaction/account/ledger restriction ahead of when it is forced by protocol 20, to observe any fallout independent of soroban. Their high-level plan is referenced here

Known limitations

[TODO or N/A]

[tsachiherman]

Fyi: #4882

[mollykarcher]

Fyi: #4882

Yep, referenced this in PR description. This is just porting that back to master branch