chore(dependencies workflow): refactor dependency conflict resolution logic

[saadanzari]

Description

Update obsolete logic in Dependencies.yaml for "Check if dependencies were changed".

Why

After the improvement done during of #1306, it is noticed that the check if the dependencies file was changed is obsolete.
The relevant steps affected by this constraint should be executed every time the workflow is triggered.

- **Dependencies Workflow**:
  - Update logic for Dependencies workflow [#1524](https://github.com/eclipse-tractusx/portal-frontend/pull/1524)

Issue

#1518

Checklist

• I have followed the contributing guidelines
• I have performed IP checks for added or updated 3rd party libraries
• I have performed a self-review of my own code
• I have successfully tested my changes locally

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[evegufy]

This is just an improvement, no fix. Just an obsolete check that can be remove not a fix, as also state in the issue #1518, please change title and description accordingly.
Please also raise PR against against, it's not at all urgent and does not need to go into the release.

[evegufy]

the type feat does imply some change to source code, which isn't the case here. I in general, I recommend you read up on the different types of conventional commits (IMO chore or build are suitable here).
also the pr title is quite redundant, referring twice to the dependencies flow, please improve.

[saadanzari]

@evegufy since there is some logic that's been modified for existing functionality, but it was in .workflow file, there was some confusion I added chore first then renamed it as feat. the requested updates are done in this PR.

[evegufy]

eclipse-tractusx/portal-assets#466 (review)