Create way for user to force a full pull on runners where a cache might have stale information after .gitattributes LFS config changes
If the user has modified their .gitattributes (e.g. whether files are lockable or not), the cache that is on the runners will not reflect the changes to the attributes and the user's flows might not behave as expected until the cache is flushed.
While there is a way to do this in the flow definition, most users get their flows from the registry and do not know/care how to modify them.
The user needs an easy way to force flushes to be cached without having to ask customer service to do it manually.