Specific column selection and api serialization

[iuwqyir]

TL;DR

Added API response serialization and improved field selection in database queries

What changed?

• Replaced Topics []string with individual topic fields (Topic0, Topic1, Topic2, Topic3) in Log struct
• Added GetTopic helper method to safely access topic fields
• Updated log decoding logic to use individual topic fields
• Added field selection support to database queries for better performance and flexibility
• Added serialization of blocks, transactions, logs to the API
• Fixed column name for access_list in transactions table
• Added new fields to BlockModel for better API documentation
• Added "deprecated" tag to decodedData field in response and replaced with decoded

How to test?

1. Run existing log decoding tests to verify topic handling
2. Test API endpoints with specific field selections
3. Verify log event decoding with indexed parameters
4. Check transaction access list functionality
5. Validate block API responses include new fields

Why make this change?

• Improved database schema efficiency by using fixed columns instead of arrays
• Better query performance through selective field fetching
• Enhanced API response consistency and documentation
• More reliable log topic handling and event decoding
• Clearer separation between storage and API models

[iuwqyir]

• create an endpoint to query token balances #136
• Handle sigterm #150
• Chain based table name and default columns configuration #151
• Use VersionedCollapsingMergeTree and insert based deletes #149
• Specific column selection and api serialization #148 👈 (View in Graphite)
• Conform getTraces to api standard #147
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.