zink/kopper: don't use generated include in kopper interface

this causes build race conditions

Reviewed-by: Adam Jackson <ajax@redhat.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15830>

src/gallium/drivers/zink/zink_instance.py

@@ -112,7 +112,6 @@ void zink_stub_${cmd.lstrip("vk")}(void);
 
 struct pipe_screen;
 struct pipe_resource;
-bool zink_kopper_update(struct pipe_screen *pscreen, struct pipe_resource *pres, int *w, int *h);
 
 #endif
 """

src/gallium/drivers/zink/zink_kopper.h

@@ -68,6 +68,7 @@ struct kopper_displaytarget
    enum kopper_type type;
 };
 
+struct zink_context;
 struct zink_screen;
 struct zink_resource;
 
@@ -106,4 +107,6 @@ bool
 zink_kopper_present_readback(struct zink_context *ctx, struct zink_resource *res);
 void
 zink_kopper_deinit_displaytarget(struct zink_screen *screen, struct kopper_displaytarget *cdt);
+bool
+zink_kopper_update(struct pipe_screen *pscreen, struct pipe_resource *pres, int *w, int *h);
 #endif

src/gallium/frontends/dri/kopper.c

@@ -30,7 +30,7 @@
 #include "state_tracker/st_context.h"
 #include "os/os_process.h"
 #include "zink/zink_public.h"
-#include "zink/zink_instance.h"
+#include "zink/zink_kopper.h"
 #include "driver_trace/tr_screen.h"
 
 #include "dri_screen.h"