Optimize RocksDB configuration for improved performance

[aso20455]

Describe your changes

I improved how our database works by fine-tuning RocksDB settings. The changes make searches faster with bloom filters, save disk space with smart compression, and reduce memory usage with better caching. Each database section (column family) now has settings matched to how it's actually used - some optimized for reading, others for writing. These improvements should make the chain run smoother without requiring any code changes.

Checklist before merging

• If this PR has some consensus breaking changes, I added the corresponding breaking:: labels
  • This will require 2 reviewers to approve the changes
• If this PR requires changes to the docs or specs, a corresponding PR is opened in the namada-docs repo
  • Relevant PR if applies:
• If this PR affects services such as namada-indexer or namada-masp-indexer, a corresponding PR is opened in that repo
  • Relevant PR if applies:

[yito88]

@aso20455 Thank you for the proposal! Do you have the result of the optimization?
Currently, I don't believe that RocksDB read/write is the bottleneck for each commit. Additionally, performance varies by node. I mean that not all operators use the same machine, and someone might prioritize the throughput/latency over the memory usage.
However, general optimization should be considered for the future. I'm really interested in your measurement result.