remove extra accounts cap call at startup (backport #27949)

[mergify[bot]]

This is an automatic backport of pull request #27949 done by Mergify. Cherry-pick of 7ddacc4bb4df29b5d1b695ddb695b1fe03e7f657 has failed:

On branch mergify/bp/v1.14/pr-27949
Your branch is up to date with 'origin/v1.14'.

You are currently cherry-picking commit 7ddacc4bb.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   ledger/src/blockstore_processor.rs

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[solana-grimes]

:scream: New commits were pushed while the automerge label was present.

[jeffwashington]

I just hit a cap mismatch here on restart on this second cap check, probably due to the race condition. Running 1.4, testing oom issues.