chore(ci): import libs

[nevermarine]

Description

import libs

Why do we need it, and what problem does it solve?

What is the expected result?

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: ci
type: chore
summary: import libs

[sourcery-ai]

Reviewer's Guide

This PR refactors the CI image build configurations by splitting dependency definitions, unifying the source checkout and package import workflow, and standardizing the installation and cleanup steps across all werf.inc.yaml files.

File-Level Changes

Change	Details	Files
Refactor dependency definitions into altPackages and packages	Split original packages list into altPackages (for apt-get) and packages (for import) Update builderDependencies template to load both altPackages and packages	images/packages/**/werf.inc.yaml
Overhaul shell install workflow	Remove SSH config and mkdir boilerplate Replace multiple git clone lines with a single git clone in install Insert importPackageImages include before install step	images/packages/**/werf.inc.yaml
Standardize package installation and cleanup	Switch apt-get install to use altPackages variable Add copy-and-remove loop to transfer package contents into image	images/packages/**/werf.inc.yaml
Adjust dependency lists across images	Moved, added or removed various -devel and library entries (e.g., libnftnl, systemd, libslirp) Sync dependency lists with new importPackageImages workflow	images/packages/**/werf.inc.yaml images/virt-launcher/werf.inc.yaml images/virt-artifact/werf.inc.yaml images/virt-handler/werf.inc.yaml images/libvirt/werf.inc.yaml images/qemu/werf.inc.yaml images/edk2/werf.inc.yaml images/dvcr-artifact/werf.inc.yaml images/dvcr/werf.inc.yaml images/base-alt-p11-binaries/werf.inc.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.