refactor : improve chatbot structure with error handling, logging, and validation

[ajaysehwal]

• Modularize code with Tokenizer and ChatBot classes
• Add logging for debugging and API request tracking
• Implement validation for model data and intents structure
• Add exception handling for model loading and response generation
• Introduce confidence threshold parameter for response accuracy
• Improve error messages and responses for API calls

[Ronnieraj37]

Hey @ajaysehwal. The changes are good and I would like to suggest something more!

The current chatbot in our app is deployed on Railway and our front-end uses the deployed link to interact with the chatbot. It works perfectly but it's just that we have to spend credits to keep it running on Railway. Can you if possible find a way to deploy this Python server along with the front-end of the app on vercel(or any platform that supports this). So that we won't need to deploy our Chatbot on a different platform.

If you're interested do create a separate Issue for this. I'll assign it to you.

[ajaysehwal]

Hey! @Ronnieraj37 Thanks for the feedback. I understand the concern about the costs of the Railway. I'll look into ways to deploy the Python server and front end together on a platform like Vercel (or something else that supports both). This will help us avoid having the chatbot on a separate platform.

I'll create a separate issue for this and dive into the details. Looking forward to working on this!