Fixes #37822 - Re-raise non-container push repo validation errors

[sjha4]

What are the changes introduced in this pull request?

Re-raise non-container push name conflict validation errors on repository saves.

Considerations taken when implementing this change?

The earlier patch was catching all validation errors and rescuing silently. Too wide a net resulting in silenced errors on other validations.

What are the testing steps for this pull request?

1. Create a product and create a repo.
2. Try creating another repo of same name.
3. You should see a proper validation error.
4. Try any other validation errors to make sure error path looks good.

To test that the container push race condition suppression still works, use steps here: #11129 (comment)

[chris1984]

Code looks fine to me and it works, @qcjames53 did you want to test the container push race condition again? I don't have podman or container stuff setup on my devel box.

[qcjames53]

Hey Samir,

The race condition that used to exist here is still solved. I'm confident in this fix continuing to address that. It looks like other errors are still going to be thrown here; beyond the testing steps, I'm going to lean on Chris' testing of the error handing for additional repo creation errors since he has already ACKed this PR.