Install module into the kernel module tree

[dhrm1k]

Add install and uninstall targets for the module.

The install target copies the built .ko into /lib/modules/<kernel>/extra
and runs depmod, so the module can be found normally by tools like
modprobe, modinfo, and modules-load.d. Without this, users have to load
the local build artifact directly with insmod.

I ran into this while testing on an Acer Aspire A315-58. I had a
modules-load.d entry for acer-wmi-battery, but each boot still logged a
module load failure because the module had only been built locally and was not
installed into the kernel module tree. After installing it under
/lib/modules/<kernel>/extra and running depmod, both
modinfo acer-wmi-battery and modprobe acer-wmi-battery resolve it correctly.

This also attaches the existing WMI device ID table to the wmi_driver
definition so the generated modalias metadata matches the GUID supported by the
driver.

I tested this with make, sudo make install, modinfo acer-wmi-battery,
and modprobe --show-depends acer-wmi-battery.

[dhrm1k]

@shadowhexer I ran into a related install/reinstall problem and was working on it. Your comment made me realize that the same work can also cover the kernel-update behavior you mentioned.

I have added a normal make install target and DKMS support: #156

The install target fixes the normal modprobe/modinfo/modules-load.d path, and the DKMS config so rebuilding/installing the module when new kernels are installed.

[shadowhexer]

@shadowhexer I ran into a related install/reinstall problem and was working on it. Your comment made me realize that the same work can also cover the kernel-update behavior you mentioned.

I have added a normal make install target and DKMS support: #156

The install target fixes the normal modprobe/modinfo/modules-load.d path, and the DKMS config so rebuilding/installing the module when new kernels are installed.

Thanks for noticing the issue and delivering a fix. I hope the module author merge this.