FEAT: Smoke Testing pip installation on Blank Docker Images

[bewithgaurav]

ADO Work Item Reference

AB#37531

---

Summary

Testing driver on minimal docker images with just python installed.
This pull request introduces smoke testing the package from PyPI.

Pipeline Enhancements:

• Added a new pipeline configuration file, pypi-package-smoketest.yml, to perform smoke tests on PyPI packages across three Linux distributions: UBI9 (RHEL), Ubuntu, and Debian. This ensures compatibility and reliability of the package across different environments.

[Copilot]

Pull Request Overview

This PR adds smoke testing for the mssql-python package on minimal Docker images and provides a Dockerfile for a UBI9‐based Python 3.12 container.

• Introduces a new Azure Pipelines config (pypi-package-smoketest.yml) that spins up UBI9, Ubuntu, and Debian containers, installs Python/pip, and runs a simple main.py test.
• Adds a Dockerfile for UBI9 Python 3.12 that creates and activates a virtual environment.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
eng/pipelines/pypi-package-smoketest.yml	CI pipeline to smoke‐test PyPI package installation on three Linux distros
Dockerfile	UBI9‐based Python 3.12 image with a preconfigured virtual environment

Comments suppressed due to low confidence (3)

eng/pipelines/pypi-package-smoketest.yml:43

• Ubuntu 22.04 and Debian 12 default apt repositories do not include Python 3.12. Attempting to install python3.12 will fail. Consider either using the system Python (e.g. python3), adding a PPA/debian backports, or aligning python_version with the distro’s available version.

                python$(python_version) \

eng/pipelines/pypi-package-smoketest.yml:30

• [nitpick] The inline shell block is quite large and repeated across matrix entries. Consider extracting these steps into a shared script file (e.g. scripts/smoketest.sh) to improve readability and reduce duplication.

    - script: |

Dockerfile:7

• [nitpick] Pinning the virtual environment path is fine, but you may want to ensure python3 always points to the expected minor version (3.12) by adding a python3.12 symlink or using the explicit binary (python3.12).

RUN python3 -m venv $VENV_PATH