Implement `db` command - Database credentials

[gander]

🎯 Implement db Command

Priority: MEDIUM (Control Tier - Tier 3)
API Endpoint: POST /db
Phase: Control Commands
Dependencies: info command (server validation)

📋 Acceptance Criteria

• Command structure implemented in Cliffy
• API integration with mikr.us /db endpoint
• Input validation and error handling
• Support for 3 output modes (default, -f, -raw)
• Secure credential display handling
• Unit tests with >80% coverage
• Integration tests with API mocking
• Security validation tests
• Documentation updated

🧪 TDD Implementation

• Write failing tests first
• Implement minimal passing code
• Refactor and optimize
• Add edge case tests

🔧 Technical Details

• Retrieves database connection credentials
• Security-sensitive information requiring careful handling
• Configuration/access information command
• May require special handling for credential display

🔗 Dependencies

• Depends on: Implement info command - Server details & specs #117 (info command) for server validation patterns
• Blocks: None (independent configuration command)

🔗 Security Considerations

• Sensitive credential information
• May need masked/redacted output options
• Secure logging requirements

🎯 Success Criteria

• Command returns database credentials securely
• Proper handling of sensitive information
• All output modes working correctly
• Test coverage >80%

Implementation Order: 7th (Control - parallel implementation possible)**

[github-actions]

🤖 Auto-Tagging Complete

This issue was analyzed but no existing labels matched the content.

Note: The following labels were suggested but don't exist in this repository yet:

• area:cli
• area:config
• area:docs
• area:security
• type:error
• area:api

Maintainers may want to create these labels for better issue organization.

These labels help organize and prioritize issues. If any labels seem incorrect, maintainers can adjust them manually.

---

This is an automated process. For questions about auto-tagging, please check the workflow documentation.

[github-actions]

🤖 Auto-Tagging Complete

This issue was analyzed but no existing labels matched the content.

Note: The following labels were suggested but don't exist in this repository yet:

• area:cli
• area:config
• area:docs
• area:security
• type:error
• area:api

Maintainers may want to create these labels for better issue organization.

These labels help organize and prioritize issues. If any labels seem incorrect, maintainers can adjust them manually.

---

This is an automated process. For questions about auto-tagging, please check the workflow documentation.