chore(ci): build more libs

[eofff]

Description

krb5: krb5-1.21.3-final -> libkrb5
lz4: v1.9.4 -> liblz4
lzo: v2.10 -> liblzo2
xz: v5.4.5 -> liblzma

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

We want more control when building libraries files, as well as making images more secure.

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: self-build for libkrb5, libzl4, liblzo2, libzma
impact_level: low

[deckhouse-BOaTswain]

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: cancelled.

[deckhouse-BOaTswain]

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: cancelled.

[deckhouse-BOaTswain]

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: cancelled.

[deckhouse-BOaTswain]

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: cancelled.

[deckhouse-BOaTswain]

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: cancelled.