Project cleanup: Delete unwanted folders and files, restructure project for clean organization

# Project Cleanup and Restructuring

## Overview
This issue tracks the cleanup and restructuring of the project to remove unwanted files/folders and organize the codebase for better maintainability.

## Current Issues Identified

### Unwanted/Temporary Files & Folders
Based on analysis of the workspace structure, the following items should be cleaned up:

1. **Cache and temporary directories:**
- `.pytest_cache/` - pytest cache files
- `tmp/` - temporary files directory
- `__pycache__/` folders throughout the project
- Cache files mentioned in gitignore patterns

2. **Log and trace files:**
- `log.txt` - application log file
- `trace.txt` - trace/debug file
- `traceback.txt` - error traceback file

3. **Development artifacts:**
- `.vscode/` - VS Code specific configuration (should be in .gitignore)
- `.venv/` - Virtual environment (should not be committed)
- `mypy.ini` - Type checking configuration (evaluate if needed)
- `pytest.ini` - Test configuration (evaluate location)

4. **Duplicate/backup folders:**
- `LoSeSb-backup/` - appears to be a backup of LoSeSb folder
- Duplicate renpy installations/versions

5. **Potentially outdated files:**
- `editor_config_suggestion.json`
- `fix_editor_config.py`
- `fix_workflows.ps1`

## Proposed Cleanup Actions

### Immediate Cleanup
1. Remove temporary and cache files
2. Delete log files (they should be generated fresh)
3. Remove backup folders if they're outdated
4. Clean up development artifacts that shouldn't be in version control

### Project Restructuring
1. Consolidate related functionality into logical directories
2. Move configuration files to appropriate locations
3. Update .gitignore to prevent future unwanted files
4. Create clear separation between:
- Core ComfyUI application code
- Extensions and plugins
- Documentation
- Examples and demos
- Build/development tools

### Suggested Directory Structure
```
ComfyUI/
├── src/ # Core application code
├── extensions/ # Plugin/extension system
├── docs/ # Documentation
├── examples/ # Example workflows and demos
├── tests/ # Test suites
├── tools/ # Development and build tools
├── configs/ # Configuration files
└── scripts/ # Utility scripts
```

## Benefits
- Reduced repository size
- Faster clone times
- Cleaner development environment
- Better project organization
- Easier navigation for new contributors
- Improved build performance

## Implementation Plan
1. Audit all files and folders for necessity
2. Create comprehensive .gitignore
3. Remove unwanted files safely
4. Restructure remaining files into logical hierarchy
5. Update documentation to reflect new structure
6. Update build scripts and CI/CD pipelines

## Testing Requirements
- Ensure no critical functionality is broken
- Verify all tests still pass
- Confirm build process works
- Test that examples and demos function correctly

## Migration Guide
Provide clear migration guide for:
- Developers with existing workflows
- Extension authors
- Users with custom configurations