feat: add comprehensive development environment setup

[DeepDN]

• Add docker-compose.dev.yml for development environment
• Add Dockerfile.dev-tools for development tools container
• Add requirements-dev.txt with development dependencies
• Add enhanced .env.dev with comprehensive development settings
• Add dev-setup.sh script for automated development setup
• Add comprehensive Makefile with development, testing, and utility commands
• Add pre-commit configuration for code quality checks
• Support for PostgreSQL and Redis in development (optional)
• Enhanced development workflow with testing, linting, and security checks

Development features:

• Hot reloading and debugging
• Comprehensive testing suite
• Code quality tools (black, flake8, isort)
• Security scanning (bandit, safety)
• Performance testing setup
• Documentation generation
• Git hooks for quality assurance

Pull Request

Description

What does this PR do?

Why is this change needed?

What problem does it solve?

Related Issues

• Fixes #
• Related to #

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)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement
• Security improvement
• Code cleanup
• Build/CI changes
• Test improvements

Changes Made

Added

Changed

Removed

Fixed

Testing

Test Environment

• Local development environment
• Docker development environment
• Docker production environment
• AWS/Cloud environment

Tests Performed

• Unit tests pass
• Integration tests pass
• Manual testing completed
• Browser compatibility tested
• Mobile responsiveness tested (if UI changes)

Test Cases

Test Results

Screenshots

Before

After

Code Review Checklist

General

• Code follows project style guidelines
• Code is well-commented and self-documenting
• No debugging code or console.log statements left
• No hardcoded values (use environment variables)
• Error handling is appropriate
• Performance impact considered

Security

• Input validation implemented
• No sensitive data exposed
• Authentication/authorization properly handled
• SQL injection prevention verified
• XSS prevention implemented

Database

• Database migrations included (if schema changes)
• Backward compatibility maintained
• Indexes added for new queries
• Data validation at model level

Frontend (if applicable)

• Responsive design implemented
• Accessibility guidelines followed
• Browser compatibility tested
• Form validation implemented
• Loading states handled

Documentation

• README updated (if needed)
• API documentation updated (if applicable)
• Code comments added for complex logic
• Changelog updated

Deployment Considerations

Environment Variables

Database Changes

• No database changes
• Migration script included
• Backward compatible changes only
• Breaking database changes (requires coordination)

Configuration Changes

Dependencies

Breaking Changes

What breaks?

Migration Path

Deprecation Notice

Additional Notes

Known Issues

Future Improvements

Questions for Reviewers

Pre-submission Checklist

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published

Post-merge Tasks

• Update deployment documentation
• Notify stakeholders of changes
• Monitor for issues in production
• Update related issues/PRs

---

Reviewers

@DeepDN

Labels

---

**Thank you for contributing to IT Asset Manager! **