In Turris OS 3.x opkg was the package containing
/etc/opkg/distfeeds.conf. This file with TOS 4.0+ was moved by upstream
to base-files. This means hat we also have to move postinst for that
file update to base-files from opkg package. This should fix OPKG feeds
being reseted by update.

Upstream prefixed manufacturer name to target config. This is somewhat
nasty of them but we should stay consistent with them. This updates our
configuration to use that target instead.

This should help us to debug system configuration better to see what
exactly was targeted version. This also helps users to see what they are
dealing with. It in some sense informs them if they are upgrading to new
version or if that is just packages change (because of configuration
change) in same release.

These are list aliases and we have them here so users with TOS 4.0-beta1
can update to future releases. With some future release we can revert
this commit and that way drop this. It does not have to exist for long
time after final release or even before it.

These are special lists intended to be used with contractors.

Note: upstream merged part of configuration to default definition. We
should probably include that as well. This does not implement that. When
this patch is about to be pushed to upstream we should integret this in
better way.

This drops problematic chunk with CMAKE_INSTALL bump. This patch is
already in our tree for one update and this chunk is causing problems
with patch application every time upstream updates procd.

I don't see a reason why we should exclude usb2 from base installation.
It is hardware support and all our devices do have usb ports so let's
support them in default in their completeness.

This is new format of repositories and it cleans little bit an idea
about what is authoritative hash we are going to use when we are tagging
new releases.