previous implementation was racy and bound to issues when more
than 1 file change request happened before worker was triggered.
using C++ move assignment is nice, but LV2 worker is a C API
that does not fit non-POD types very well, leading to awkward
implementations alike before with current + staged + deleted models.
let us "downgrade" to raw pointers, which are C compatible.
since LV2 worker rules are well defined, any crashes or racy
behaviour can be considered host-side bugs.
Signed-off-by: falkTX <falktx@falktx.com>
falkTX