feat(api): move calculation of scratch filesystem overhead to cdi controller

[Isteb4k]

Description

CDI always requests scratch space with a Filesystem volume mode, regardless of the volume mode of the related
DataVolume. An additional overhead space should be reserved for the Filesystem volume.

By default, this overhead is taken from the CDI Config and is not dynamically updated based on the target PVC size.
As a result, the target PVC size with the overhead from the CDI Config may be insufficient to successfully complete
PVC creation.

To address this, since there is no strict formula for ext4 filesystem overhead, empirical estimates of the filesystem
overhead were provided based on the target PVC size:

• return 0 for target PVC size == 0
• add 40% for target PVC size < 24Mi
• add 25% for target PVC size < 512Mi
• add 15% for target PVC size < 4096Mi
• add 10% for target PVC size >= 4096Mi

Previously, this overhead was added at the level of our controller, which led to an undesirable increase in the size of images and disks. As part of this PR, the addition of an overhead is now taking place at the cdi controller level.

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.