Added dashbot features

[saisreesatyassss]

Pull Request Description

Summary

This PR introduces new enhancements to API Dash, focusing on improving debugging, API documentation generation, and response visualization. These features align with the discussions in Issue #621 and contribute to the broader vision of DashBot as an AI-powered assistant for API Dash.

---

Features Implemented

1. Multi-Model Selection (Google Maps & Snowflake)

• Added support for selecting multiple models like Google Maps and Snowflake within API Dash.

• Enables seamless integration and switching between different models for enhanced flexibility.

• Screenshot:
  

• Video Demonstration: Multi-Model Selection Demo (https://drive.google.com/file/d/1vJcrqLwmMukxqWaaDPXI4WUGF7iBQB2q/view?usp=sharing)

2. Debug Requests Based on Status Codes & Error Messages

• Introduced an intelligent debugging system that analyzes API responses.
• Provides insights into errors by categorizing them based on status codes and error messages.
• Enhances developer productivity by offering suggestions for quick issue resolution.
• Screenshot:
  

3. Generate API Documentation

• Added functionality to auto-generate API documentation based on request and response structures.
• Formats and presents the API details in an easy-to-read manner.
• Screenshot:
  
• Video Demonstration: API Documentation Generation (https://drive.google.com/file/d/106bYvU0aeMzEE4dj3UGWvX1mDcwrF6I2/view?usp=sharing)

4. Generate Plots & Visualizations for API Responses

• Enables users to visualize API response data through customizable charts and plots.
• Supports customization options for better data representation.
• Screenshot:
  
• Video Demonstration: API Visualization Demo (https://drive.google.com/file/d/1eZdwxFqo6sB4IY8ZhrdFAK5PDHLNf4pR/view?usp=sharing)

---

Notes & Discussion

I know this may not be the perfect way to implement it, but I created a separate backend to call API endpoints and used it to interact with LLMs instead of using Flutter packages directly. Since I couldn’t include API keys in the PR, I avoided hardcoding them.

However, if there's a better way to integrate LLM-based features in API Dash while keeping API keys secure, I’m open to suggestions. Would using Flutter plugins for direct LLM calls be a better approach, or should we continue with a backend-based API call system? Looking forward to feedback!

---

Related Issues

• Pull Request Title (Open)
• Issue Title (Open)

Checklist

• I have gone through the contributing guide
• I have updated my branch and synced it with project main branch before making this PR
• I am using the latest Flutter stable branch (run flutter upgrade and verify)
• I have run the tests (flutter test) and all tests are passing

Added/updated tests?

We encourage you to add relevant test cases.

• Yes
• No, and this is why: I will add the tests for the module once the approach is verified.

OS on which you have developed and tested the feature?

• Windows
• macOS
• Linux