CV2-5391: use save instead of save! to avoid raising error

[melsawy]

Description

Based on CV2-5324 there is a method to check Relationship exists before creating a new one but may the failure related to other validation so I use a save instead of save! to avoid raising error

References: CV2-5391

How has this been tested?

Re-run automated tests.

Things to pay attention to during code review

Please describe parts of the change that require extra attention during code review, for example:

• File FFFF, line LL: This refactoring does this and this. Is it consistent with how it’s implemented elsewhere?
• Etc.

Checklist

• I have performed a self-review of my own code
• I have added unit and feature tests, if the PR implements a new feature or otherwise would benefit from additional testing
• I have added regression tests, if the PR fixes a bug
• I have added logging, exception reporting, and custom tracing with any additional information required for debugging
• I considered secure coding practices when writing this code. Any security concerns are noted above.
• I have commented my code in hard-to-understand areas, if any
• I have made needed changes to the README
• My changes generate no new warnings
• If I added a third party module, I included a rationale for doing so and followed our current guidelines

[caiosba]

Agree, Sawy... This is good for race conditions.

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ ActiveRecord::RecordNotUnique: PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "relationships_least_... Sidekiq/SmoochWorker View Issue
• ‼️ ActiveRecord::RecordNotUnique: PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "relationships_least_... Sidekiq/Sidekiq::Extensions::DelayedClass View Issue

_{Did you find this useful? React with a 👍 or 👎}