CONFIG_CUSE missing?

### Description

colima version 0.5.2
git commit: 6b5b6fe0540e708f0c9d6e8919fab292c671fc72

runtime: docker
arch: x86_64
client: v23.0.1
server: v20.10.20

```
colima:~$ modprobe -l | grep fuse
kernel/fs/fuse/fuse.ko
kernel/fs/fuse/virtiofs.ko
colima:~$ modprobe cuse
modprobe: module cuse not found in modules.dep
```

and:

```
colima:~$ sudo modprobe configs
colima:~$ zcat /proc/config.gz | grep CONFIG_FUSE
CONFIG_FUSE_FS=m
CONFIG_FUSE_DAX=y
colima:~$ zcat /proc/config.gz | grep CONFIG_CUSE
# CONFIG_CUSE is not set
```

Is cuse not enabled? Trying to test a build of libfuse where this is required: `test/test_examples.py::test_cuse FAILED`

How can I get a kernel with cuse?

The issue is about the Linux kernel configuration in Colima's VM missing CONFIG_CUSE, which is needed for libfuse tests. Check how Colima builds or selects its kernel image, likely in the lima or VM provisioning code. Look for kernel config files or build scripts in the repository. Enabling CUSE requires rebuilding the kernel or adjusting the config, then testing that the module loads and the libfuse test passes.

Escrito por el modelo de indexación a partir del texto del issue.