Reorganize Falco fork

[Stringy]

There was a significant amount of friction and lost time when updating the Falco fork. To combat this, it should be reorganized in such a way as to make updates easier and make it easy to remove patches that are unneeded or have been upstreamed.

The proposed procedure is:

• make the main branch track upstream/master
• extract stackrox patches onto module version branches (e.g. release-2.4 or similar) on top of the main branch.
• Current master, and previously tagged module versions will remain until they are out of support (up to module version 2.4.0, collector 3.14.1, ACS 4.0)

This can be simulated on separate branches before committing to the approach, but should be done before existing patches are removed or modified.

[Stringy]

Holding off on this until post 4.1 release for fork stability