Implement a `purge-repos` command to CLI for purging old repos based on time

[anisurrahman75]

[anisurrahman75]

➤ make build && ./bin/kubectl-stash-linux-amd64 purge-repos --storage-config /home/anisur/Desktop/backend-conf.yaml --older-than 1s
making bin/kubectl-stash-linux-amd64

I0918 12:46:15.713755 102150 purge_repos.go:267] Starting repository purge operation
I0918 12:46:15.713790 102150 purge_repos.go:268] Configuration file: /home/anisur/Desktop/backend-conf.yaml
I0918 12:46:15.713797 102150 purge_repos.go:269] duration filter: 1s (cutoff: 2025-09-18T12:46:14+06:00)
I0918 12:46:15.713801 102150 purge_repos.go:270] Dry run mode: false

🔎 Searching for repositories. This may take a while depending on the number of repositories...

⚠️ Some repositories could not be processed:

• repository diff-encryption: Fatal: wrong password or no key found

Found 10 repositories to purge:

REPOSITORY LAST MODIFIED AGE

---

s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-01 2025-09-18 10:32:42 2h 14m
s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-02 2025-09-18 10:32:57 2h 14m
s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-03 2025-09-18 10:33:12 2h 13m
s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-04 2025-09-18 10:33:27 2h 13m
s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-05 2025-09-18 10:33:42 2h 13m
s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-06 2025-09-18 10:33:56 2h 13m
s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-07 2025-09-18 10:34:12 2h 12m
s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-08 2025-09-18 10:34:26 2h 12m
s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-09 2025-09-18 10:34:41 2h 12m
s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-10 2025-09-18 10:34:57 2h 12m

This will permanently delete 10 repositories. Are you sure? (y/N): y

🔥 Starting repository deletion. This process can be lengthy, please do not interrupt.

===== Snapshot Deletion Summary =====

✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-01: all snapshots purged
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-02: all snapshots purged
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-03: all snapshots purged
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-04: all snapshots purged
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-05: all snapshots purged
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-06: all snapshots purged
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-07: all snapshots purged
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-08: all snapshots purged
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-09: all snapshots purged
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-10: all snapshots purged

Cleaning up storage metadata...
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-01: metadata deleted
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-02: metadata deleted
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-03: metadata deleted
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-04: metadata deleted
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-05: metadata deleted
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-06: metadata deleted
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-07: metadata deleted
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-08: metadata deleted
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-09: metadata deleted
✅ s3:https://s3.us-east-2.amazonaws.com/kubestash/vaimo/repo-10: metadata deleted

===== Final Summary =====
Operation completed in 4m8.99540907s
Successfully deleted: 10 repositories
Success rate: 100.0%