Add exclusive lock to ensure only one pipeline is created

What does this MR do and why?

This is to fix the issue so that only one pipeline is created and updated when server receives two requests at the same time from snyk.

The solution is simply use exclusive lock to ensure one pipeline will be created during the same period.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #13134 (closed)