feat(error-handling): restructure error handling module with enhanced types and sanitization

[Endowed992]

Description

Closes #427

Closes #429

This pr implements a refactor for chainLogistics service modules

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ x] 🔧 Code refactor (no functional changes)
• 📚 Documentation update
• 🧪 Tests (adding or updating tests)
• 🔒 Security (security-related changes)
• 🚀 Performance (performance-related changes)
• 🎨 UI/UX (user interface changes)
• 🛠️ DevOps (deployment, CI/CD, infrastructure changes)

Changes Made

The split is now complete with:

code.rs
response.rs
sanitize.rs
types.rs
conversions.rs
mod.rs

Updates:

Added Uuid import in types.rs
Added focused AppError unit tests
Updated docs references from backend/src/error.rs to error

Code Changes

Documentation Updates

Database/Schema Changes

Testing

Manual Testing

Automated Tests

• [ x] Unit tests pass
• [ x] Integration tests pass
• [x ] E2E tests pass (if applicable)
• [x ] Performance tests pass (if applicable)

Test Coverage

Screenshots/Videos (UI Changes)

Before	After

Breaking Changes

Checklist

Code Quality

• [ x] Code follows project style guidelines
• [x ] Code is self-documenting or properly commented
• [x ] No console.log statements or debugger breakpoints left
• [ x] No unused imports or variables
• [x ] Code passes linting checks

Testing

• [x ] Unit tests added/updated for new functionality
• [x ] Integration tests added/updated if needed
• [x ] Manual testing completed
• [ x] Edge cases considered and tested
• [ x] Tests pass locally

Documentation

• [ x] README updated if needed
• [x ] API documentation updated if needed
• [x ] Inline code documentation added/updated
• [x ] Comments added for complex logic

Security

• [x ] Security implications reviewed
• [ x] No sensitive data exposed
• [ x] Input validation added where needed
• [ x] Authentication/authorization considered

Performance

• [ x] Performance impact assessed
• [x ] No performance regressions introduced
• [x ] Bundle size checked (frontend)
• [x ] Database queries optimized (backend)

Deployment

• Environment variables documented
• Database migrations included
• Backward compatibility maintained
• Rollback plan considered

Legal/Compliance

• DCO (Developer Certificate of Origin) signed
• License headers added to new files
• Third-party dependencies reviewed
• GDPR/privacy implications considered

Related Issues

Additional Context

[vercel]

@Endowed992 is attempting to deploy a commit to the Ebeleokolo's projects Team on Vercel.

A member of the Team first needs to authorize it.

[Lynndabel]

@Endowed992 please resolve conflict

[Lynndabel]

@Endowed992 whats the update?