Figure out what to do with denoiser lib

[gabcoh]

Need to compile the model into it, but also should it be in a different repo? If so we need to scrub the history here or decide what to do about that

[MatthewScholefield]

We probably don't need to worry about the source code for the alpha testers, but in general, my thoughts were that we could do something like:

• Have the open source repo be code has #include "denoiser/denoiser.h" with a public interface and just blank functions in denoiser.cpp
• We use a build flag to specify the folder of the denoiser. So by default we have this blank denoiser code in like src/denoisers/blank (so src/denoisers/blank/denoiser/denoiser.h).
• Then for our releases we specify an out of tree path or some other path for our custom denoiser module.
• Ultimately, someone could develop an rnnnoise denoiser module that we might include in the public source.
• As for the logistics of the generated module header, that can be a script or something we run in our custom denoiser module repo and then we don't include any generated sources in any repo.