Re-implement `Task` WebApp

[emrgnt-cmplxty]

As we are in the process of re-implementing our Task management system, we should also focus on bringing back the Task WebApp that provided a friendly interface for users to interact with our task server. The WebApp was previously designed to work seamlessly with the Task server, providing an easy way to create, manage, and view tasks.

Key features of the previous implementation were:

• APITask Class: A class to encapsulate the details of a task, including the task ID, model, main configuration, instruction configuration, helper agent names, toolkits, instructions, status, and error. This class also had methods to create an APITask object from the server's response data and to strip the task ID from the object.

• Submit New Task Function: This function used to create a new APITask object from the agent store's state and send a POST request to the /task/initialize endpoint to initialize a new task.

• Get Task by ID Function: This function used to send a GET request to the /task/<task_id> endpoint to fetch the details of a task by its ID.

• Get Task Logs by ID Function: This function used to send a GET request to the /task/logs/<task_id> endpoint to fetch the logs of a task by its ID.

• Get Task Summaries Function: This function used to send a GET request to the /task_summaries endpoint to fetch the summaries of all tasks.

We need to re-implement the WebApp with these functionalities, taking into account any changes made to the server's API endpoints. In addition to the re-implementation, we should focus on enhancing the WebApp with a better user experience, improved error handling, and additional features.

Here are some points to consider for the re-implementation and enhancement:

• User Experience: The WebApp should provide a friendly and intuitive user interface, guiding the users through the process of creating, managing, and viewing tasks.

• Error Handling: The WebApp should handle any errors that may occur during the interaction with the server and provide clear and helpful error messages to the users.

• Code Quality: The code should be well-structured, easy to understand, and maintainable. It should follow best practices and coding standards for JavaScript and React (if we're using React for the front-end).

• Additional Features: Consider adding more features to the WebApp, such as a way to edit or delete tasks, filter or sort the list of tasks, view detailed task logs, etc.

Requested Action

The goal of this issue is to reintroduce the Task workflow into our codebase, taking the positives from the previous implementation, addressing its weaknesses, and ensuring it suits our current and future needs. We encourage contributions to this effort and welcome discussion on the best ways to go about it.

The image below is screenshot showing a limited view into the original demo.

As always, don't hesitate to ask if you have any questions or need further clarification. I can provide the old front end code as a starting point. Your contributions to this project are highly valued!