Upstream renamed it to config.buildinfo.

They also introduced new file feeds.buildinfo. We could use that instead
of our git-hash generated file.

This moves all options from Omnia support patch to common configs. They
are all part of kernel support for packages so it should be enabled on
all our routers. This ensures that. It also means that there is one less
patch to rebase and maintain.

This also moves some stuff around in common kernel configuration.

This patch is not valid because it patches 4.14 kernel but mvebu is
switched to 4.19 but for now let's have it as it is before compilation
of tools for aarch64 is fixed.

This package was disabled in 9098d37c
without explanation. Let's try to reebable it to see if it works or what
it breaks.

Upstream changed names of variables in /etc/os-release to correspond to
correct project name. It is no longer Lede but once again OpenWRT.

Configuration override options was misleading. In reality those are
options you most probably don't want to mess too much with so let's call
them rather advanced options.

This also moves PUBLISH_BRANCH in example configuration file to
section: don't mess with. This is because now we provide it from
defaults and user just should not mess with it unless he know what he is
doing.

OpenWRT commit to be used is specified in feeds.conf file with rest of
feeds now so it makes not sense to overwrite it. This is just confusing
without any real gain in here. You can always modify feeds.conf file to
achieve the same.

This makes sure if there isn't this package, the build fails
Also, reorder section Turris packages

We have to ensure that languages are installed when module is installed.
It does not matter if that is done immediately or later but it has to be
done. The solution in here is to check if module is installed and if so
also request languages for it.

This is just basically rebase of those patches on top of 4.19 kernel.
It seems that there is no change in this case between 4.14 and 4.19.

This adds code that is not pkglists dependent and when any Foris plugin
is installed it should automatically also maintain languages.

Note that lists are not aware of Foris packages existence so they need
list of all existing plugins.