explain static builds in DIY section

We technically don't need the extractor to be a static build,
but we *want* people/packagers to use one of our static builds.
We should make that clear in this section too, instead of giving vague pointers.

Yes, there is a note about static builds and a link to the FAQ in a section above.
No reason to be that vague for people scrolling directly to the details for DIY/packaging.

When I (as a packager) read "requires a static .. binary" I think  "no I can make a dynamic build myself just fine" (which works)
and reading "We have these versions available" I understand that as "For people that are not at all able to build these from source".