Add groff package to all environments

What does this merge request do and why?

This MR broadens the scope of our package_*.txt files. We have been using this approach for the GRD base image for a while and it comes with the benefit to reduce maintenance efforts, as we reuse the list of packages to install.

It also adds groff as a dependency for all systems.

Doesn't this potentially increase image sizes

Yes, potentially. There may be packages in the packages_*.txt files which are not really used in one particular container and are only there for historical reasons. Any such size difference is minuscule in comparison to the images using two entirely different base images - Ubuntu vs. Debian.

This MR does not solve the linked issue completely.

It does in particular nothing related to auditing any of the package lists.

It does, however, help to ensure a consistent environment by reusing the same package list for all Debian-based environments, so that auditing becomes less work.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Impacted categories

The following categories relate to this merge request:

• gdk-reliability - e.g. When a GDK action fails to complete.
• gdk-usability - e.g. Improvements or suggestions around how the GDK functions.
• gdk-performance - e.g. When a GDK action is slow or times out.

Merge request checklist

• This MR references an issue describing the change.
• This change is backward compatible. If not, please include steps to communicate to our users.
• Tests added for new functionality. If not, please raise an issue to follow-up.
• Documentation added/updated, if needed.
• Announcement added, if change is notable.
• gdk doctor test added, if needed.

Contributes to #2967