ingest/ledgerbackend/configs: Update default captive core config

[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 reviewed the changes in this PR and if I consider them worthwhile for being mentioned on release notes then I have updated the relevant CHANGELOG.md within the component folder structure. For example, if I changed horizon, then I updated (services/horizon/CHANGELOG.md. I add a new line item describing the change and reference to this PR. If I don't update a CHANGELOG, I acknowledge this PR's change may not be mentioned in future release notes.
• 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

Replace Whalestack with Creit Technologies in default pubnet captive core config.

Why

This will make the quorum set in the default captive core config match the tier 1 validator list:

https://stellarfoundation.slack.com/archives/C02U19A2A/p1735930631316469

Known limitations

[N/A]

[sreuland]

lgtm, this config doesn't get loaded by any integration testing correct just for runtime validation, a quick way to confirm this may be horizon --network pubnet I assume?

[sreuland]

lgtm, this config doesn't get loaded by any integration testing correct just for runtime validation, a quick way to confirm this may be horizon --network pubnet I assume?

oh, nice, there is test coverage on this config , thanks!

[tamirms]

a quick way to confirm this may be horizon --network pubnet I assume?

@sreuland yes, running that command and observing the logs would be the best way to verify that the quorum set is functional.