quickseal 0.1.4

Create Kubernetes SealedSecrets with a single secure command
Documentation
## Description

<!-- Provide a brief description of the changes in this PR -->

## Type of Change

<!-- Mark the relevant option with an "x" -->

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] Documentation update
- [ ] Performance improvement
- [ ] Code refactoring
- [ ] Dependency update

## Related Issues

<!-- Link to related issues using #issue_number -->

Closes #

## Changes Made

<!-- List the specific changes made in this PR -->

-
-
-

## Testing

<!-- Describe the testing you've performed -->

- [ ] Unit tests added/updated
- [ ] Integration tests added/updated
- [ ] Manual testing performed
- [ ] All tests pass locally (`cargo test`)

### Test Commands

```bash
# Commands used to test these changes
cargo test
cargo clippy
cargo fmt --check
```

## Constitution Compliance Checklist

<!-- Verify compliance with the Rust CLI Development Constitution v1.0.0 -->

### Principle II: Security-First Development
- [ ] No security vulnerabilities introduced (`cargo audit` passes)
- [ ] Sensitive data handled securely (zeroed memory, secure temp files)
- [ ] No secret values logged

### Principle III: Code Quality Standards (NON-NEGOTIABLE)
- [ ] Code formatted with `cargo fmt`
- [ ] No clippy warnings (`cargo clippy` passes)
- [ ] Result types used for error handling (no unwrap/expect in library code)
- [ ] No panics in library code

### Principle IV: Testing & Documentation Requirements
- [ ] Test coverage ≥70% (run `cargo llvm-cov` or `cargo tarpaulin`)
- [ ] Public APIs have rustdoc comments with examples
- [ ] All tests pass (`cargo test --all`)
- [ ] Documentation builds (`cargo doc --no-deps`)

### Principle V: Build & Cross-Platform Compatibility
- [ ] Builds without warnings on Linux, macOS, Windows
- [ ] Platform-specific code properly gated with `#[cfg(...)]`

## Performance Impact

<!-- Describe any performance implications -->

- [ ] No performance regression
- [ ] Performance improvement (describe)
- [ ] Performance impact acceptable (justify)

## Breaking Changes

<!-- If this is a breaking change, describe the impact and migration path -->

N/A

## Screenshots/Logs

<!-- If applicable, add screenshots or relevant log output -->

## Additional Notes

<!-- Any additional information for reviewers -->

## Checklist

- [ ] My code follows the project's code style
- [ ] 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

## Reviewer Notes

<!-- Notes for reviewers about areas of focus or concern -->