Feature Request: incremental refresh for warehouse with container image repos using NewestBuild strategy

[Brightside56]

Checklist

• I've searched the issue queue to verify this is not a duplicate feature request.
• I've pasted the output of kargo version, if applicable.
• I've pasted logs, if applicable.

Proposed Feature

I'm using dockerhub webhook receiver (I'm using other registry, but I've made webhook translator service to make its webhooks compatible with dockerhub), and when webhook arrives, Kargo seems to be refreshing warehouse in general, and since I'm using NewestBuild strategy for container images repository, refresh still takes 60s and issues hundreds of queries to registry to get metadata of all tags in repo

Proposal is to perform incremental refresh (which will perform metadata calls only to specific tag from webhook) in case when it's originated from webhook

Motivation

Developer experience improvements, reduction of resources usage

[github-actions]

This issue has been automatically marked as stale because it had no activity for 90 days. It will be closed if no activity occurs in the next 30 days but can be reopened if it becomes relevant again.

[krancour]

We don't currently have a way for any of the artifact discovery logic to have any awareness of how it was initiated: i.e. regularly scheduled, vs refreshed by a user, vs refreshed by a webhook. #5213 proposes something for this, but I'm not sure where we will land with that yet.

Regardless of what may happen with #5213, I believe that #5298 should provide some significant relief in this scenario without needing to impart the artifact discovery process with any awareness of how it was triggered, so I'm going to tentatively close this.