Split Notcurses into Notcurses-core and Notcurses

[KristofferC]

Notcurses allows you to build a core library (notcurses-core) which does not require you to depend on ffmpeg and a full library notcurses which depends on ffmpeg and gives some multimedia support. Perhaps it makes sense to mimic that in the jlls.

What that would entail in practice would be two jlls, one Notcurses_core_jll providing libnotcurses-core and libnotcurses-ffi library and a Notcurses_jll provoding the libnotcurses library. Notcurses_jll would depend on Notcurses_core_jll.

Does that make sense to you @giordano?

[giordano]

I think it does make sense, yes. We do something similar for HarfBuzz: we have a base package and the ICU one which also depends on ICU_jll (which is a complicated dependency as it breaks the ABI very frequently), useful because very few packages depend on the ICU variant, while the base one is way more popular. This is inspired by what many Linux distributions do with HarfBuzz