[DLStreamer] CI reorganization - aligning and merging DLS Pipeline Server to DLS

[dmichalo]

Description

Please include a summary of the changes and the related issue. List any dependencies that are required for this change.

Fixes # (issue)

Any Newly Introduced Dependencies

Please describe any newly introduced 3rd party dependencies in this change. List their name, license information and how they are used in the project.

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Checklist:

• I agree to use the APACHE-2.0 license for my code changes.
• I have not introduced any 3rd party components incompatible with APACHE-2.0.
• I have not included any company confidential information, trade secret, password or security token.
• I have performed a self-review of my code.

[nszczygl9]

In my opinion, the current workflow is complex and difficult to understand for team members who aren't familiar with DLS/DLSPS CI processes. Since we already build the DLStreamer image separately for DLSPS, I believe we could improve readability by splitting this into separate, parallel workflows. For example, we could have one PR workflow dedicated to DLS and another for DLSPS, both triggered simultaneously. Or we can separate scans to another workflow and build and test in main worfklow (?) Just a suggestion. @tbujewsk let us know what do you think

[tbujewsk]

In my opinion, the current workflow is complex and difficult to understand for team members who aren't familiar with DLS/DLSPS CI processes. Since we already build the DLStreamer image separately for DLSPS, I believe we could improve readability by splitting this into separate, parallel workflows. For example, we could have one PR workflow dedicated to DLS and another for DLSPS, both triggered simultaneously. Or we can separate scans to another workflow and build and test in main worfklow (?) Just a suggestion. @tbujewsk let us know what do you think

I agree, let's split it into two separate workflows.

[dmichalo]

Separation implemented - both DLS and DLS PS have similar main PR action dls[ps]-pr-workflow.yamls which triggers next actions and workflows.