fpm fails on oss build

[spalger]

There is currently an issue building Kibana when both --oss and --os-packages flags are used.

fpm is tripping up on a very funky path in node_modules:

Processing files: kibana-oss-8.0.0_SNAPSHOT-1.x86_64 {:level=>:info}
error: File not found: /var/folders/64/zw1v56gj4_141lvs5q88z5_40000gn/T/package-rpm-build-334e0ab2394b133a5ebec245770a1302355b7262651ba36e0ffe4b31d24f/BUILD/usr/share/kibana/node_modules/@elastic/eui/lib/components/icon/assets?lazy?recursive?^\.\/.[*]\.js[$] {:level=>:info}
{:level=>:info}
{:level=>:info}
   Macro expanded in comment on line 24: %undefine __check_files {:level=>:info}
RPM build errors: {:level=>:info}
{:level=>:info}
   File not found: /var/folders/64/zw1v56gj4_141lvs5q88z5_40000gn/T/package-rpm-build-334e0ab2394b133a5ebec245770a1302355b7262651ba36e0ffe4b31d24f/BUILD/usr/share/kibana/node_modules/@elastic/eui/lib/components/icon/assets?lazy?recursive?^\.\/.[*]\.js[$] {:level=>:info}

The file node_modules/@elastic/eui/lib/components/icon/assets?lazy?recursive?^\.\/.[*]\.js is being created by the CleanClientModulesOnDLLTask in the build, when it's trying to make sure that the entry points into the DLL are still on disk for webpack to find when it rebuilds. While deleting all other files from a node module.

It's unclear why the DLL only has this entry point in the oss build (the default dist doesn't even seem to have an eui entry point).

[elasticmachine]

Pinging @elastic/kibana-operations