chore: add hacky configuration for nightly test runs

Recently the configuration of blink changed in a way that broke the
integration-tests for the nightly version (which I run locally). This
means I cannot use them to drive development, because ci also needs to
use the stable version.

Work around this by adding a hacky configuration for the nightly
version. I think if it's being used in the stable version, it should
just get ignored.

This should not stay here for a long time - I think I'll be able to
remove it when the next stable version of blink is released.

integration-tests/test-environment/.config/nvim/init.lua

@@ -37,6 +37,9 @@ local plugins = {
     event = "VeryLazy",
     -- use a release tag to download pre-built binaries
     version = "v0.*",
+
+    -- to (locally) track nightly builds, use the following:
+    -- dir = "/Users/mikavilpas/git/blink.cmp/",
     ---@module 'blink.cmp'
     ---@type blink.cmp.Config
     opts = {
@@ -58,6 +61,7 @@ local plugins = {
           },
         },
       },
+      -- configuration for the stable version of blink
       windows = {
         autocomplete = {
           max_height = 25,
@@ -69,6 +73,27 @@ local plugins = {
           max_width = 200,
         },
       },
+
+      -- 2024-11-28 configuration for the nightly version of blink. mikavilpas
+      -- uses this for local development, but currently ci uses the stable
+      -- version
+      --
+      ---@diagnostic disable-next-line: missing-fields
+      completion = {
+        ---@diagnostic disable-next-line: missing-fields
+        documentation = {
+          ---@diagnostic disable-next-line: missing-fields
+          window = {
+            desired_min_height = 30,
+          },
+          auto_show = true,
+          auto_show_delay_ms = 0,
+        },
+        ---@diagnostic disable-next-line: missing-fields
+        menu = {
+          max_height = 25,
+        },
+      },
     },
   },
   {