feat(cli): validate storage settings at startup

[yongkangc]

Add validation to error when CLI storage flags differ from persisted settings, instead of silently ignoring user input.

Closes #20482

Users changing storage flags (e.g., --static-files.receipts) after genesis get no feedback - the node silently uses stored settings.

Solution

Compare CLI settings against stored settings at startup. On mismatch, return actionable error:

Storage settings mismatch!

Stored in DB: { receipts_in_static_files: false, ... }
From CLI:     { receipts_in_static_files: true, ... }

Storage flags cannot be changed after genesis.
Either remove the conflicting CLI flags, or delete the database and re-sync.

• Validation in CLI layer, not storage layer (keeps ProviderFactory simple)
• Only compares CLI-configurable fields via static_file_settings_eq() - RocksDB flags are ignored since they're not exposed in CLI

[yongkangc]

blocked by #20393