[Documentation]: Create comprehensive migration guide for v2.0.0 breaking changes

## Description

Create comprehensive documentation to help users migrate from v1.x to v2.0.0, which will include significant dependency management changes and potential breaking changes.

## Type of Issue

- [ ] Bug report
- [ ] Feature request
- [x] Documentation
- [ ] Question/Support
- [ ] Enhancement

## Documentation Requirements

### Migration Guide Content

1. **Overview of Breaking Changes**
- Dependency changes (peer dependencies migration)
- API changes (if any)
- Configuration changes (if any)
- Behavioral changes

2. **Step-by-Step Migration Instructions**
- Pre-migration checklist
- Installation command updates
- Code changes required
- Configuration updates
- Verification steps

3. **Dependency Management Changes**
- New peer dependencies: `reflect-metadata`, `class-validator`
- Optional peer dependencies: `pino` (for PinoDbLogger users)
- Installation examples for different package managers (npm, yarn, pnpm, bun)
- Version compatibility matrix

4. **Common Migration Issues**
- Troubleshooting dependency conflicts
- Handling missing peer dependencies
- Version mismatch resolution
- Bundle size optimization tips

5. **Before and After Examples**
- Installation commands comparison
- Import statement changes (if any)
- Configuration changes (if any)

## Deliverables

- [ ] Create `MIGRATION.md` file in repository root
- [ ] Update main `README.md` with migration notice
- [ ] Add migration guide link to package.json homepage/docs
- [ ] Include migration information in release notes template

## Acceptance Criteria

- [ ] Migration guide covers all breaking changes in v2.0.0
- [ ] Step-by-step instructions are clear and actionable
- [ ] Examples provided for all major use cases
- [ ] Troubleshooting section addresses common issues
- [ ] Documentation is reviewed and approved before v2.0.0 release

## Additional Context

This documentation should be created before the v2.0.0 release and will serve as the primary resource for users upgrading from v1.x versions. The migration guide should be comprehensive enough that users can confidently upgrade without breaking their existing applications.

## Related Issues

- #26 - Move appropriate dependencies to peer dependencies
- Any other v2.0.0 breaking change issues

## Priority

High - Required before v2.0.0 release

Start with related issue #26 and review the v2.0.0 breaking changes before drafting MIGRATION.md in the repository root. Update README.md, package.json, and the release notes template as listed, covering the dependency changes and migration steps. Done means the guide addresses the acceptance criteria and is ready for review before the v2.0.0 release.

Written by the indexing model from the issue text.