[Update] Refactor YAML Handling, Enhance Trace Data Structure, and Improve Pipeline

[patrick204nqh]

Description

This PR introduces several significant changes and improvements:

• Refactored YAML Handling: Removed YAML formatters and refactored the YamlTransformer to build hierarchical hashes while transforming keys and values.
• Enhanced Trace Data Structure:
  • Introduced traits for depth, time tracking, and identification.
  • Improved depth assignment methods.
  • Added a new TraceLinker for better linking of method calls and returns.
• Pipeline Updates: Reorganized trace pipeline by reordering the linking step before depth assignment and renaming methods for better clarity.
• Added New Features:
  • Solarized theme support for action colors in the tracer.
  • Helper modules for configuration, colorization, and tracking, enhancing modularity and consistency.
• Bug Fixes:
  • Updated validation logic for truncate_length to ensure it is an integer.
  • Fixed issues related to class tracing and diagram generation.
• Performance and Developer Experience:
  • Disabled/enabled Bundler caching in CI workflows for optimization.
  • Introduced IDGenerator for unique ID generation.
  • Enhanced logging and exporting mechanisms with LoggingManager and ExportManager.

Type of Change

Check all that apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change that adds functionality)
• Documentation update
• Breaking change (fix or feature that changes existing behavior)
• Other (please describe):

How Has This Been Tested?

Describe the tests you ran to verify your changes:

• Ran bundle exec rspec to ensure all tests pass.
• Added or updated specs for new functionality.
• Verified changes on supported Ruby versions and environments.
• Manual testing for specific features like export formats and colorization.

Checklist

• I have followed the [Ruby Style Guide](https://github.com/rubocop/ruby-style-guide).
• I have performed a self-review of my code.
• I have added or updated tests as needed.
• All existing and new tests pass.
• I have updated the documentation (if needed), including README.md and CHANGELOG.md.
• I have considered the impact on users and documented any required changes or upgrades.

Deployment Notes

No special deployment changes are required once this PR is merged.

Related Issues

N/A

Screenshots (if applicable)

N/A