Language catch 22

[alerque]

Current makefile load order:

1. casile.mk
2. Project rules file(s)
3. rules.mk

Now, where do we load localized make variables? Currently in №3, because languages are set by project (or CLI run) most reasonable in №2. That leaves them unusable in №2. Which mean projects can't avail themselves of localized strings.

Obviously the current makefile hackery to even have localized strings is, well, dirty. We should come up with something cleaner, preferably moving localization to Fluent and loading strings earlier to be used earlier too.

[alerque]

This could get resolved by moving some configuration parameters from being Makefile variables to YAML or TOML based project configs. In that event they could be read early and defaults supplied after without screwing up GNU Make's Makefile processing order.

[alerque]

This is resolved in v0.4.1. Put language: <code> into a YAML config file and save as casile.yml. It's processed early on (before make even gets its grubby fingers on anything).