[FEATURE] Implementation of the General Peer

## 📝 What needs to be done?
Implement the General Peer API, which will remain a point of contact for all other peers.
The functions to be developed are-
1) Function(s) handling General peer functionality during training phase of model.
2) Function(s) handling General peer functionality during query phase.

## 🎯 Which part of the project?

- [ ] 🧠 AI/ML Models (AI components and machine learning)
- [x] � Backend (Core server logic and APIs)
- [ ] 🌐 Frontend (CLI & React.js user interface)
- [x] 🌐 Network Layer (P2P networking and communication)
- [ ] 🔗 Shared Utilities (Common code and libraries)
- [ ] 📚 Documentation
- [ ] 🧪 Testing
- [ ] 🛠️ Development tools

## 🔧 What type of work is this?

- [x] ✨ New feature
- [ ] 🐛 Bug fix
- [ ] 💅 UI/Design improvement
- [ ] 📚 Documentation
- [ ] 🧪 Testing
- [ ] 🔧 Code cleanup/refactoring
- [ ] 🚀 Performance improvement

## ✅ How do we know when this is done?
All newly implemented functions/APIs work independently with appropriate return values, given some initial test data.

- [ ] Required functions implemented
- [ ] Consistent JSON return values
- [ ] Proper error handling for improper input.

## 🌟 How important is this task?

- [ ] 🔥 Critical - Blocks other work
- [ ] 🎯 High - Important for next milestone
- [x] 😊 Medium - Should be done soon
- [ ] 🤷 Low - Nice to have

## ⏱️ How much time might this take?

- [ ] ⚡ Quick (less than 1 hour)
- [ ] 🏃 Short (1-4 hours)
- [ ] 🚶 Medium (4-8 hours / 1 day)
- [x] 🐢 Long (2-3 days)
- [ ] 🏔️ Big project (more than 1 week)

## 🧪 Testing needed

- [x] 🧪 Unit tests (test individual functions)
- [ ] 🔗 Integration tests (test how parts work together)
- [x] 👤 Manual testing (human testing)
- [ ] 📱 Test on different devices/browsers
- [ ] ⚡ Performance testing
- [ ] 🔒 Security testing
- [ ] ❌ No testing needed

## 📚 Documentation needed

- [] 💬 Code comments
- [ ] 📖 README updates
- [ ] 📚 User guide
- [x] 👨‍💻 Developer documentation
- [ ] ❌ No documentation needed

---