Allow obsoletion of protected packages

This is the libdnf5 companion to
rpm-software-management/libdnf#1610; if we
change DNF 4, then we should also change DNF 5.

There should be some mechanism for replacing even protected packages,
e.g. to upgrade DNF to DNF 5. We unprotected dnf to allow this upgrade,
but that solution isn't perfect; DNF 5 should be able to remove
python3-dnf[1] and DNF 4 should not be able to remove DNF without
installing DNF 5. @m-blaha proposed "implementing a hard-coded
self-protection for each package manager", i.e. adding back the
hardcoded protection of dnf and python3-dnf in DNF 4 and adding a
protection of dnf5 in DNF 5. So if we want to do this, it seems we would
need to allow obsoletion of protected packages to allow DNF 4 to
obsolete dnf with dnf5.

The running kernel is treated as a special case; obsoletes of the
running kernel are still not allowed.

libdnf5/rpm/solv/goal_private.cpp

@@ -580,11 +580,8 @@ libdnf5::GoalProblem GoalPrivate::protected_in_removals() {
  auto & pool = get_rpm_pool();
 
  libdnf5::solv::SolvMap pkg_remove_list(pool->nsolvables);
- for (auto index = 0; index < removes.size(); ++index) {
- pkg_remove_list.add_unsafe(removes[index]);
- }
- for (auto index = 0; index < obsoleted.size(); ++index) {
- pkg_remove_list.add_unsafe(obsoleted[index]);
+ for (const auto & remove : removes) {
+ pkg_remove_list.add_unsafe(remove);
  }
 
  libdnf5::solv::SolvMap protected_pkgs(pool->nsolvables);
@@ -593,6 +590,13 @@ libdnf5::GoalProblem GoalPrivate::protected_in_removals() {
  }
  if (protected_running_kernel.id > 0) {
  protected_pkgs.add_unsafe(protected_running_kernel.id);
+ // Special case: consider the obsoletion of the running kernel as a
+ // removal. Obsoletion of other protected packages should be allowed.
+ for (const auto & obsolete : obsoleted) {
+ if (obsolete == protected_running_kernel.id) {
+ pkg_remove_list.add_unsafe(obsolete);
+ }
+ }
  }
 
  removal_of_protected.reset(new libdnf5::solv::SolvMap(std::move(pkg_remove_list)));