Changing package warning as errors additional args (#8705)

**Context:**
Bug fix for the issue found in (#8699) :
`pytest-benchmark causes a collection failure when using pytest-xdist.
Since this is now on by default, we must skip the benchmarking runs
explicitly when running the WAE reporter action.`

The `--benchmark-disable` flag isn't being passed to the unit tests
despite the previous fix.

**Description of the Change:**
Updating `interface-unit-test` so that `pytest_additional_args` gets
used.

**Benefits:**
The flags passed using `pytest_additional_args` gets used.

**Possible Drawbacks:**
None.

**Related GitHub Issues:**
PennyLaneAI/plugin-test-matrix#116
#8699

---------

Co-authored-by: Yushao Chen (Jerry) <[email protected]>

Author: runora95

.github/workflows/interface-unit-tests.yml

@@ -109,7 +109,7 @@ jobs:
       - name: Set pytest arguments for setting warnings level
         id: pytest_warning_flags
         env:
-          PYTEST_WARNING_ARGS: -W "${{ inputs.python_warning_level }}" --continue-on-collection-errors
+          PYTEST_WARNING_ARGS: -W "${{ inputs.python_warning_level }}" --continue-on-collection-errors "${{ inputs.pytest_additional_args }}"
         run: |
           if [ "${{ inputs.python_warning_level }}" != "default" ]; then
             echo "Setting pytest warning flags"

doc/releases/changelog-dev.md

@@ -517,6 +517,9 @@ A warning message has been added to :doc:`Building a plugin <../development/plug
 
 <h3>Bug fixes 🐛</h3>
 
+* Update `interface-unit-tests.yml` to use its input parameter `pytest_additional_args` when running pytest.
+  [(#8705)](https://github.com/PennyLaneAI/pennylane/pull/8705)
+
 * Fixes a bug where in `resolve_work_wire_type` we incorrectly returned a value of `zeroed` if `both work_wires` 
   and `base_work_wires` were empty, causing an incorrect work wire type.
   [(#8718)](https://github.com/PennyLaneAI/pennylane/pull/8718)