Update functional correctness tests to support renamed CSV files

[EnekoGonzalez3]

The current functional correctness tests are outdated due to changes in the naming of CSV files, making it impossible to continue the original verification process. A new test proposal is needed to ensure the following checks are performed:

1. Message Storage Validation: Ensure that every message generated by the client is stored in the correct file, corresponding to its chronicle and story name.
2. Timestamp Range Check: Verify that the timestamp of each message falls within the expected range of [story_chunk_start, storychunk_end(, ensuring proper data segmentation.
3. Message Sorting by Timestamp: Ensure all messages within a file are correctly sorted by their timestamp.

To achieve this, the client_admin tool will be used for personalized real-time message sending, and the data string format will follow the pattern: chroniclename_storyname.