Make health checks more considerate

[notfirefox]

For reference, this is my current blink.cmp config:

return {
    "saghen/blink.cmp",
    dependencies = { "L3MON4D3/LuaSnip", version = "v2.*" },
    version = "1.*",
    opts = {
        cmdline = { enabled = false },
        completion = {
            documentation = {
                auto_show = true,
                auto_show_delay_ms = 200,
            },
            menu = {
                draw = {
                    columns = {
                        { "label" },
                        { "kind" },
                    },
                    components = {
                        label = {
                            text = function(ctx)
                                return ctx.label
                            end,
                        },
                    },
                },
            },
        },
        fuzzy = { implementation = "lua" },
        keymap = { preset = "enter" },
        snippets = { preset = "luasnip" },
    },
}

This is the :checkhealth output that I get:

blink.cmp:                                 require("blink.cmp.health").check()

System ~
- ✅ OK curl is installed
- ✅ OK git is installed
- ✅ OK Your system is supported by pre-built binaries (x86_64-unknown-linux-gnu)
- ✅ OK blink_cmp_fuzzy lib is downloaded/built

Sources ~
- ⚠️ WARNING Some providers may show up as "disabled" but are enabled dynamically (i.e. cmdline)

Default sources ~
- snippets (blink.cmp.sources.snippets)
- lsp (blink.cmp.sources.lsp)
- buffer (blink.cmp.sources.buffer)
- path (blink.cmp.sources.path)

Disabled sources ~
- omni (blink.cmp.sources.complete_func)
- cmdline (blink.cmp.sources.cmdline)

Two thinks that I would like to object here.

1. If I use the lua implementation of the fuzzy matcher, I am clearly not concerned whether my system is supported by the pre-built binaries and whether blink_cmp_fuzzy is downloaded/built. I think it would be great if we could skip such steps if the user intentionally does not use the rust fuzzy matcher implementation.
2. I intentionally disabled cmdline option and yet I am warned about the fact that the cmdline source may be loaded dynamically. The warning also isn't very clear to me. Is it just cmdline that may be enabled dynamically, or does this affect other sources as well. And if it is just cmdline, wouldn't it make sense to silence the warning when disabling it?

So as you can tell, those are mostly nitpicks. My impression overall has been largely positive with blink.cmp and I have been able to switch from nvim-cmp to it without missing much. But as I was revising my Neovim config and checked the :checkhealth output, this is just something I came across of. I thought I would drop this as some sort of feedback here.