Make config linking non-unique

[qwerty287]

closes #3093

[codecov]

Codecov Report

Attention: 12 lines in your changes are missing coverage. Please review.

Comparison is base (d815b20) 34.82% compared to head (7bc950a) 34.87%.
Report is 13 commits behind head on main.

Files	Patch %	Lines
pipeline/backend/kubernetes/kubernetes.go	0.00%	11 Missing ⚠️
pipeline/backend/kubernetes/pod.go	93.75%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3128      +/-   ##
==========================================
+ Coverage   34.82%   34.87%   +0.04%     
==========================================
  Files         228      228              
  Lines       14755    14772      +17     
==========================================
+ Hits         5139     5152      +13     
- Misses       9238     9242       +4     
  Partials      378      378              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[6543]

we should not do that ... this is a hotfix at most!!

@qwerty287 could you check why the dublication did ocured in the first place.

or at lesat add a dedicated pipelineConfigID and retrive it based on that.

this table is just for n-m relation mapping and such should never have a dublicate!!!

[qwerty287]

Well, I know that this shouldn't occur, but in this case, it was 100% expected.

Just add two yaml files with exactly the same content (yes, I know this isn't a common use case).

This triggers the unique constraints and fails, but I think it should work without issues.

[6543]

I found the root cause

so i created a fix and add tests for that #3215