Changes proposed ✍️

What

🤖 Generated by Copilot at 2012ef2

This pull request implements a new feature that allows users to view and manage merge suggestions for organizations that have the same identity. It adds and modifies code in the backend, the frontend, and the search sync worker to generate, store, fetch, and update the merge suggestions and the no-merge status of organization pairs. It also adds new tables, routes, handlers, services, methods, and components for this feature. It modifies the env file to change the log level for debugging.
​

🤖 Generated by Copilot at 2012ef2

Organizations
Merge or ignore by identity
Autumn of duplicates

Why

How

🤖 Generated by Copilot at 2012ef2

• Add two new routes to the organization API for getting and updating the merge suggestions based on the same identity (link)
• Add new files for the handlers of the new routes, which implement the logic for calling the OrganizationService methods (link, link)
• Add a new route to the tenant API for getting the organizations that have merge suggestions (link)
• Add a new file for the handler of the new route, which implements the logic for calling the TenantService method (link)
• Add a new migration file for creating two new tables in the database for storing the merge suggestions and the no-merge status (link)
• Add new imports and lines of code to the mergeSuggestionsWorker function, which runs periodically to generate the merge suggestions based on the same identity and store them in the database (link, link, link, link)
• Add new blocks of code to the organizationService file, which define the methods for generating and managing the merge suggestions and fetching the organizations that have merge suggestions (link, link)
• Add new blocks of code to the tenantService file, which define the method for fetching the organizations that have merge suggestions for the current tenant (link)
• Add a new route and a new import to the organization-routes file, which define the route and the component for the organization merge suggestions page in the frontend (link, link)
• Add new blocks of code to the organization-service file, which define the methods for updating the no-merge status and fetching the organizations that have merge suggestions in the frontend (link, link)
• Add a new router-link element to the organization-list-page component, which links to the organization merge suggestions page and shows the number of merge suggestions (link)
• Remove a router-link element from the organization-list-page component, which linked to the organization import page (link)
• Add a new computed property to the organization-list-page component, which checks if the edit is locked for sample data (link)
• Add a new line of code to the onMounted hook of the organization-list-page component, which calls the method for fetching the number of merge suggestions (link)
• Add a new file for the organization-merge-suggestions-page component, which implements the logic and the UI for the organization merge suggestions feature in the frontend (link)
• Add new properties to the IDbOrganizationSyncData interface, which define the shape of the organization data for the search sync worker, including the weak identities, the merge suggestions, and the no-merge status (link, link)
• Add new blocks of code to the OrganizationRepository class, which define the subqueries and the joins for fetching the merge suggestions and the no-merge status of the organizations from the database (link, link)
• Add new properties to the InitService class, which mock the organization identity data, the merge suggestions, and the no-merge status for testing purposes (link, link)
• Add new blocks of code to the OrganizationSyncService class, which prepare and format the weak identities, the merge suggestions, and the no-merge status data for the Opensearch service (link, link)
• Modify a line of code in the env file, which sets the log level to 'trace' for debugging purposes (link)

Checklist ✅

• Label appropriately with Feature, Improvement, or Bug.
• Add screehshots to the PR description for relevant FE changes
• New backend functionality has been unit-tested.
• API documentation has been updated (if necessary) (see docs on API documentation).
• Quality standards are met.