Hotfix: Update content_id logic in metadata update function

[panchicore]

Modified the content_id handling to include a fallback when it is not provided. This ensures proper fallback to a test description with result_id and revision_name, preventing potential issues with missing IDs.

Pull Request Description

What

The test description was not displayed on validation report evidences.
https://validmind.slack.com/archives/C04U7TKHH62/p1746749735016559

Why

A condition was missing for content_id while logging test result description.

How to Test

1. Run a validation notebook
2. Link evidences for the risk assessment and check the test description of the evidences

Pull Request Dependencies

External Release Notes

Deployment Notes

Hotfix for validmind-library

Breaking Changes

Screenshots/Videos (Frontend Only)

Checklist

• PR body describes what, why, and how to test
• Release notes written
• Deployment notes written
• Breaking changes identified
• Labels applied
• PR linked to Shortcut
• Screenshots/videos added (Frontend)
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)

Areas Needing Special Review

Additional Notes

[cachafla]

Looks good, I suggest testing scenarios where result_id is non-empty and empty.

What was the version of this change before it broke?

[AnilSorathiya]

Looks good, I suggest testing scenarios where result_id is non-empty and empty.

Will add tests for these.

What was the version of this change before it broke?

2.8.21

[github-actions]

PR Summary

This pull request introduces a comprehensive suite of unit tests for the TestResult and related classes in the validmind project. The tests cover various aspects of the TestResult, ErrorResult, TextGenerationResult, and ResultTable classes, including initialization, method functionality, and serialization. Additionally, the PR refines the log_async method in the result.py file to improve the handling of logging tasks, particularly by separating the conditions for logging tables, figures, and descriptions. This change ensures that each component is logged only if it is present, and it corrects the handling of content_id in metadata updates.

Key changes include:

• Addition of unit tests for RawData, ResultTable, ErrorResult, TestResult, and TextGenerationResult classes.
• Mocking of asynchronous API calls to test logging functionality without actual network requests.
• Refinement of the log_async method to separate the logging of tables, figures, and descriptions, and correct the content_id handling in metadata updates.

Test Suggestions

• Run all newly added unit tests to ensure they pass successfully.
• Test the log_async method with various combinations of tables, figures, and descriptions to verify correct task creation.
• Verify that the content_id is correctly formatted and used in metadata updates.
• Check the behavior of the validate_log_config method with both valid and invalid configurations.
• Ensure that the mocked API calls in the tests are correctly simulating the expected responses.