Api Clean up, Documentation and Standarization part five

[Marinovsky]

Description

• Clean up to some classes
• Standardization to camel case in the request and response classes to the API
• Improvement of unit tests
• Addition of API class responses for live/portfolio/read and live/insights/read
• Renaming in the endpoints backtests/orders/read, live/list, live/orders/read, live/logs/read
• Update to some API class responses

Related Issue

Closes #7893

Motivation and Context

With theses changes, the C# API response class of some endpoints will be updated

Requires Documentation Change

N/A (Already done)

How Has This Been Tested?

There were already unit tests in the classes ProjectTests.cs, OptimizationTests.cs and LiveTradingTests.cs that asserted the behavior of these endpoints. Those tests were updated and expanded to assert new scenarios.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Refactor (non-breaking change which improves implementation)
• Performance (non-breaking change which improves performance. Please add associated performance test and results)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Non-functional change (xml comments/documentation/etc)

Checklist:

• My code follows the code style of this project.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

[Martin-Molinero]

Thank you! 🚀