CI: create exit log

[michal-shalev]

What?

Improves reporting across multiple CI scripts to provide clear information on the CI environment and the details required for reproducing issues.

Why?

Locating Docker info, identifying the machine, and gathering CI details is time-consuming, requiring repeated searches through logs.
This change consolidates all relevant information into a single log section on script exit, simplifying and speeding up debugging, making it easier to replicate the CI environment for troubleshooting.

How?

• Added a log_info_on_exit function triggered by trap "log_info_on_exit" EXIT in various CI scripts.
• Collects and displays the information that is listed below.

Information printed in log_info_on_exit

1. Script Information:
   Script name
   Current working directory
   User running the script
2. Machine Information:
   Whether it's running inside a container
   Container hostname
   Container image details
   Docker-specific environment variables
   Host machine name (if not in a container)
   Operating system and version
   Kernel version and details
   System architecture
3. UCX Environment Variables
4. UCX Info:
   Detailed output from ucx_info if available
5. Modules Loaded
6. CPU Affinity
7. Ulimit Information
8. System resource limits (ulimit settings)
9. Disk Usage
10. Current disk usage information

[michal-shalev]

/azp run UCX PR

[azure-pipelines]

Pull request contains merge conflicts.