Physical layouts' kscan drivers may conflict when CONFIG_PM_DEVICE=n

[joelspadin]

If you build the zmk_uno shield with CONFIG_PM_DEVICE=n, then both the matrix and direct kscan drivers are initialized and enabled. Since these two drivers are mutually exclusive (they use the same pins), this breaks key scanning.

If CONFIG_PM_DEVICE=y, then the driver for the unselected physical layout is suspended and disconnects itself, so the selected layout works correctly.