Bugfix: Add duplicate organization name check

[NenadPantelic]

Description

Added handling of the situation when the user tries to create the new organization with the name of some other persisted organization. Fixes #110.

Type of Change:

• Code

Code/Quality Assurance Only

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

1. Tested through Swagger UI:
2. Added unit test to cover this scenario

Checklist:

• [x] My PR follows the style guidelines of this project
• [x] I have performed a self-review of my own code or materials
• [x] I have commented my code or provided relevant documentation, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] Any dependent changes have been merged

Code/Quality Assurance Only

• [x] My changes generate no new warnings
• [ ] My PR currently breaks something (fix or feature that would cause existing functionality to not work as expected)
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [ ] Any dependent changes have been published in downstream modules

[NenadPantelic]

@mtreacy002 I solved the organization name conflict too (this time it is an organization, not a program :joy: ). I expect to face merge conflicts after #189 is merged (they tackle the same files).

[mtreacy002]

@NenadPantelic , can you please give us update on this?

[NenadPantelic]

Sorry for the delay, I'm busy with other things. I can update this in the next two or three days. Is that OK? The same goes for #189

[mtreacy002]

Sure, @NenadPantelic. Thanks for responding. Will look forward to the update. Don't forget to resolve the conflict while you're at it 😉.

[mtreacy002]

@NenadPantelic , can we please get the updates on this?

[devkapilbansal]

Hi @NenadPantelic are you still working on this?

[NenadPantelic]

Hey, I have been busy for the past few months. I'll do my best to finish this up or to close the MR.