HDDS-12580. Set up Temporary RocksDB for Storing Container Log Information

[sreejasahithi]

What changes were proposed in this pull request?

This change introduces the setup of temporary RocksDB storage and creates two key tables to store container log data for debugging purposes within Ozone. Also implemented codec class to serialize and deserialize data for both tables.

The two tables are as follows:

1. Container Log Table (ContainerLogTable):
        Key: Container ID
        Value: A list of ContainerInfo objects that store:
        Container's final state
        Datanode ID
        Final BCSID

2.   Datanode Container Log Table (DatanodeContainerLogTable):
        Key: Container ID and Datanode ID combination
        Value: A list of DatanodeContainerInfo objects containing:
        Timestamp of the state transition
        Container state (e.g., OPEN, CLOSED, CLOSING, QUASI_CLOSED, UNHEALTHY, DELETED ....)
        BCSID
        Error message (optional)

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-12580

How was this patch tested?

Tested this locally with sample log files.

Below is the workflow link that passed successfully:
https://github.com/sreejasahithi/ozone/actions/runs/13832960621

[errose28]

Thanks for working on this @sreejasahithi. Would it be better to use a SQL DB here instead of RocksDB? dn-container.log files are already row and column based, so they easily map to a tabular format. A SQL DB would give us much more flexibility with our queries, while with RocksDB we would be limited to whatever wrappers we create to work with the binary value formats.

[sreejasahithi]

@errose28 , Thanks for the suggestion! I'll give it a try with SQLite and see how it performs.