fix(agent): optimize of base agent

[cinjoseph]

Description

1. optimize the content format for the agent's memory access. Previously, the Agent's memory stored check_fail_reason as an action. However, check_fail_reason is more like an observation.
2. ConversableAgent add name prefix, To confirm which APP an Agent originates from in a cascading app scenario
3. Conversable supports the force_retry option. The force_retry allows users to control the next action within the act method, thereby implementing the REACT.
4. optimize the tool_assistant_agent. Make mach clearer of the prompts for ToolAction. and add the dynamic description of ToolAssistantAgent
5. implement function get_last_message in DefaultGptsMessageMemeory

How Has This Been Tested?

Snapshots:

Include snapshots for easier review.

Checklist:

• My code follows the style guidelines of this project
• I have already rebased the commits and make the commit message conform to the project standard.
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• Any dependent changes have been merged and published in downstream modules

[yhjun1026]

r+

[yhjun1026]

ConversableAgent add name prefix, To confirm which APP an Agent originates from in a cascading app scenario。There are some questions about this modification. Agents can overload and define their own names. In theory, there is no need to add name processing including prefixes to the base class.

[cinjoseph]

@yhjun1026 I think the current design is based on the assumption that there is only one of each type of Agent within the same context. In my current scenario, one app can call another app, and if both apps contain the same type of Agent, I won't be able to distinguish which app an Agent comes from in places where the Agent name is displayed. I think that Agent names shouldn't be fixed or directly tied to their Roles. The Role only represents their species, but there are many different individuals within a species. It's like how we are all humans (Role), yet we have different names.

[csunny]

This name is different to understand. Maybe it's better to use . or - such as:
Report.ChatReport or Report-ChatReport?