Removed redundant Ubuntu-specific build workflow;

updated pip install flag

The project's CI configuration experienced two main updates:
- The Ubuntu-specific Python package build workflow was entirely
removed, likely due to standardization across different environments or
redundancy with other existing workflows.
- Python package installation in the main workflow was amended to
include the `--break-system-packages` pip flag, which indicates a shift
in handling dependencies that may conflict with system packages.

These changes may streamline the CI/CD process and address dependency
conflicts during package installation.

.github/workflows/python-package-ubuntu.yml

@@ -1,42 +0,0 @@
-name: Python package build on Ubuntu
-
-on: [push, pull_request]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest 
-
-    steps:
-    - name: Update package list
-      run: |
-        sudo apt-get update
-
-    - name: Install git
-      run: |
-        sudo apt-get install -y git
-
-    - name: Checkout repository
-      uses: actions/checkout@v2
-      with:
-        submodules: 'recursive'
-
-    - name: Set up Python 3.10
-      uses: actions/setup-python@v2
-      with:
-        python-version: "3.10"
-
-    - name: Prepare Python environment
-      run: |
-        pip install --upgrade pip h5py setuptools wheel build
-
-    - name: Install dependencies
-      run: |
-        sudo apt-get install -y libhdf5-dev limesuite liblimesuite-dev automake gcc pkg-config build-essential python-is-python3
-
-    - name: Install the package
-      run: |
-        pip install .
-
-    - name: Test if the package can be imported
-      run: |
-        python -m limedriver

.github/workflows/python-package.yml

@@ -26,7 +26,7 @@ jobs:
 
     - name: Install the package
       run: |
-        pip install .
+        pip install . --break-system-packages
 
     - name: Test if the package can be imported
       run: |