feat：upgrade modelcontextprotocol 0.1.0-preview.5

[geffzhang]

1、upgrade ModelContextProtocol 0.1.0-preview.5
2、Add ModelContextProtocol.AspNetCore

[GGHansome]

Auto Review Result:

### 代码审查总结
**变更概述**: 
- The changes primarily involve code cleanup and improvements in organization and clarity. By removing unnecessary code, like the `Arguments` property, and restructuring namespaces and service registration, the code now reflects a more accurate and maintainable representation of the intended functionality.
- Specific changes include deleting outdated comments, unused code and cleaning up redundant `using` statements, as well as changing some method parameters to adhere to C# conventions.
- Additionally, small logical corrections, such as adjusting the condition for `unit_price`, were made.

### 发现的问题

**问题1: 缺少对删除字段的文档更新**
- **描述**: The removal of the `Arguments` property from `McpServerConfigModel` needs to be communicated in associated documentation or change logs, as it can impact integration for developers relying on this model.
- **建议**: Add documentation to reflect the removal of this property and update related components if they depend on `Arguments`.
  
**问题2: 代码清洁和组织**
- **描述**: Some removed comments were actually useful documentation for understanding the logic, like the detailed server setup. Removing them might cause a loss of context for future developers.
- **建议**: Consider maintaining a detailed setup guide in form of a README file or developer documentation within the repository.

**问题3: 逻辑问题**
- **描述**: In `PlaceOrder.cs`, the unit price should not be less than zero, but the error thrown is regarding missing arguments, which is not consistent for invalid values.
- **建议**: Update the error message to reflect invalid value rather than missing argument.
- **示例**: 

// 修改前
if (unit_price < 0)
{
throw new McpServerException("Missing required argument 'unit_price'");
}
// 修改后
if (unit_price < 0)
{
throw new McpServerException("Invalid value for 'unit_price'");
}

### 总体评价
Overall, the code changes enhance the maintainability and clarity of the project, adhering mostly to best programming practices. However, the removal of some comments and the property should be handled with appropriate documentation or alerts to the developers who interact with the system. Continuous documentation and consistent error messaging will make the codebase more robust in the long term.

[GGHansome]

Auto Review Result:

Code Review Summary

Change Overview: The code changes primarily focus on restructuring and cleaning up the codebase. This includes removing unused properties, reorganizing import statements, adjusting method implementations, and simplifying application logic. Changes also involve modifications in annotations within the tools for clarity and adherence to coding standards.

Identified Issues

Issue 1: Unused Property Removal

• Description: In the McpServerConfigModel, the Arguments property was removed, indicating it was likely unused. This change can streamline the model and improve performance if the property was unnecessary.
• Suggestion: Ensure that removing this property does not affect any existing functionality that might rely on it implicitly.

  // Before
  public string[]? Arguments { get; set; }
  // After
  // Property removed

Issue 2: Correct Order and Completeness of Imports

• Description: Import statements have been adjusted for better organization and completeness.
• Suggestion: Continuously maintain tidy import statements and remove any unused imports to optimize build times.

  // Before
  using BotSharp.Core.MCP.Managers;
  using ModelContextProtocol.Configuration;
  // After
  using ModelContextProtocol;
  using BotSharp.Core.MCP.Managers;
  using BotSharp.Core.MCP.Services;

Issue 3: Annotation Consistency

• Description: Corrected attribute properties from lowercase to PascalCase (e.g., name to Name) in tool annotations.
• Suggestion: Maintain consistency in naming conventions to enhance readability and maintainability across the codebase.

  // Before
  [McpServerTool(name: "make_payment")]
  // After
  [McpServerTool(Name = "make_payment")]

Issue 4: Logical Error in Condition

• Description: In PlaceOrder.cs, adjusted a logic condition checking for unit_price. Previously, it incorrectly allowed zero values.
• Suggestion: Verify all logical conditions to ensure they accurately represent the intended business rules.

  // Before
  if (unit_price <= 0)
  // After
  if (unit_price < 0)

Overall Evaluation

The code changes generally improve the modularity and clarity of the existing system. By removing unused code and restructuring existing segments, the codebase becomes more maintainable. However, special care must be taken to ensure that these changes do not introduce regressions or disrupt existing functionality. Future improvements might focus on enforcing consistent coding standards and improving test coverage to maintain robustness.