Make `runDepmod` behave more like `build-image-kernel-modules`

This CL adds the following to `prebuilt_kernel_modules`
1. System_deps property. This will be copied to the intermediates
   directory for running depmod, but will not be installed as part of
   this module. The use case for this is vendor_dlkm which depends on
   system_dlkm
2. Copy .ko files to staging directory based on their final install
   location on device.

More details on (2):
At ToT, the .ko files are copied to
$intermediates/lib/modules/0.0/*.ko

The resulting modules.dep is
foo.ko: bar.ko baz.ko

However, android devices do not have a single dlkm partition,
/lib/modules/, but we have split dlkm partitions. To ensure that the
modules.dep file resembles the paths on device, the .ko files will be
copied to the the following

$intermediates/lib/modules/0.0/system/lib/modules/*.ko
$intermediates/lib/modules/0.0/vendor/lib/modules/*.ko
$intermediates/lib/modules/0.0/odm/lib/modules/*.ko

The resulting modules.dep is
/vendor/lib/modules/foo.ko: /vendor/lib/modules/bar.ko
/system/modules/lib/baz.ko

Bug: 377562851
Test: verified that modules.* files are bit-identical for system_dlkm,
vendor_dlkm, odm_dlkm between kati and soong for aosp CF (top of CL
stack)

Change-Id: I000b45dcba041b03d86fb971d45b54147250148e