Remove id as Primary Key from the orgs table

[kalroy]

Signed-off-by: Kallol Roy karoy@progress.com

🔩 Description: What code changed, and why?

We need to remove the Primary Key constraint on org name from the org table.
This is to allow same orgs across different servers to be added.

⛓️ Related Resources

#5857

👍 Definition of Done

👟 How to Build and Test the Change

Prerequisites:
You need to have 2 infra servers Server1 and Server2. Both should have org with name Org1

• rebuild components/infra-proxy-service/
• start_all_services
• Add Server1 to Infra Server
• Add Org1 to Server1
• Add Server2 to Infra Server
• Add Org1 to Server2

✅ Checklist

All PRs must tick these:

• I have read the CONTRIBUTING document.
• All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

• Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
• Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
• Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
• Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
• Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

• Tests added/updated? (all new code needs new tests)
• Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.

📷 Screenshots, if applicable

[netlify]

👷 Deploy Preview for chef-automate processing.

🔨 Explore the source changes: 9749c1d

🔍 Inspect the deploy log: https://app.netlify.com/sites/chef-automate/deploys/6177cea884cfaf00078c6534

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information