Extend package minor upgrade tests to ensure transition from old bb

1) The minor upgrade test logic has different modes, importantly "all" (all produced packages are installed and upgraded), and "server" (the minimal set of packages is installed and upgrade, basically just mariadb-server and those which it pulls as dependencies).
The old buildbot runs both variants, the foundation buildbot only runs "server". It needs to be changed to "all".
The "server" mode has its small merits and can be added later, but "all" is more important.
We won't activate "deps" test mode which exists in the old bb, as it hasn't shown any results in the past, and besides its scope is a small subset of what "all" minor upgrade, only implemented in a different way.

2) Our general policies are such that we don't add new dependencies in minor releases unless absolutely unavoidable. The test needs to be extended to compare dependencies between the new packages and the last released ones. It is particularly important at the buildbot transition time, since the new binaries will be built on different machines.
The old buildbot has the logic for ldd comparison, but the test should do more than that, and compare also package requirements. The ldd logic also needs to be improved.

3) The current test logic excludes Columnstore from the upgrade test, because it doesn't follow the same policies as the rest of the server, and also known to be unstable. The old buildbot runs Columnstore upgrade test separately, the foundation buildbot doesn't, so there is no upgrade for Columnstore at all. We can try to add Columnstore back to the common test and see how it goes, if it's still as bad as it used to be, the separate step will have to be added.

4) Dependency checks in minor upgrade tests do not cover galera. We should try to include it, but since it's not currently done in the old buildbot either, it's better be done by a separate commit.

possibly TBC