Harden RocksDB retry detection and error accounting

[Solanasol233]

PR description

Replace RocksDB retry decisions that relied on exception message text with status-code based checks, and harden retry accounting in StorageExceptionManager.

This change keeps busy-retry handling stable across RocksDB upgrades, avoids throwing when a StorageException has no cause, and ensures the retry counter is only incremented for retryable RocksDB statuses. Focused tests cover both the busy-status helper and the retryable error accounting path.

Fixed Issue(s)

Thanks for sending a pull request! Have you done the following?

• Checked out our contribution guidelines?
• Considered documentation and added the doc-change-required label to this PR if updates are required.
• Considered the changelog and included an update if required.
• For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

• spotless: ./gradlew spotlessApply
• unit tests: ./gradlew build
• acceptance tests: ./gradlew acceptanceTest
• integration tests: ./gradlew integrationTest
• reference tests: ./gradlew ethereum:referenceTests:referenceTests
• hive tests: Engine or other RPCs modified?