Validate refresh-interval to be greater than 0

[Sbragul26]

What this PR does,

• Adds validation to ensure --refresh-interval is greater than 0
• Prevents invalid values (like 0 or negative durations) that could cause tight loops

Related issue

• Fixes Add Validation for audit-logs refresh-interval to be greater than 0 #668

[rshdhere]

Nice, this addresses the issue cleanly 👍 validating --refresh-interval upfront avoids accidental tight loops and makes the behavior safer.

Small UX thought (non-blocking): since Harbor CLI is Cobra-based, would it be worth returning this as a flag validation error (e.g. via PreRunE / returning an error) instead of log.Fatalf, so the CLI exits with a consistent usage/error message like other commands? what are your thoughts @NucleoFusion

Not required for this PR — overall this looks straightforward and well-scoped.

[Sbragul26]

Thanks for the kind words and the suggestion,

Agreed — using Cobra’s error handling (e.g. PreRunE / returning an error) would be more idiomatic and provide a more consistent CLI UX. For this PR, I aimed to keep the change minimal and focused on validating the interval, but I’d be happy to follow up or adjust this if maintainers feel that’s preferred.

[NucleoFusion]

I think the current check is enough, but we may need the duration to be more than 1s of 0.5sec or something.
We wouldnt want the user to put something so small