Step2 of Project merging to kubewaden-ui: Separate CI test for kubewarden and sbomscanner

Before move the sbomscanner UI extension code into kubewarden-ui project code base, we need to add some logic to identify which UI extension code has been changed in order to automatically trigger the corresponding CI test.

Expectation: No regression issue on original kubewarden-ui's unit test and git actions