HCAP-1349: modification to cohort participants query

[alva-fresh]

https://freshworks.atlassian.net/browse/HCAP-1349

In test db the query was selecting multiple entries for the same participant possibly due to JOIN. After setting SELECT COUNT(DISTINCT "participants"."id")" the number of available seats became correct for both queries. This request is for filtering out duplicates which causing incorrect count. Yet I don't like this solution, so happy to hear thoughts on this

Including 2 possible solutions here as separate commits based on further findings: https://teams.microsoft.com/l/message/19:IUaAmNEwTGmcqt3CjlNCrc_j7pTI3rB5QRpVrTFxNHQ1@thread.tacv2/1663206188323?tenantId=5b973f99-77df-4beb-b27d-aa0c70b8482c&groupId=3f22a178-b2af-4d1a-99cd-bc1781c11210&parentMessageId=1663204501914&teamName=HCAP&channelName=General&createdTime=1663206188323&allowXTenantAccess=false

[arranfw]

Does this mean the earlier query was fine and the larger number was incorrect?

[alva-fresh]

@arranfw you're totally right - the previous query was fine, although it did fix some inconsistencies in dev. Now this issue is not happening in dev anymore, but still present in test

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
0.0% Duplication

[alva-fresh]

closing this pull request as per discussion: https://teams.microsoft.com/l/message/19:IUaAmNEwTGmcqt3CjlNCrc_j7pTI3rB5QRpVrTFxNHQ1@thread.tacv2/1663281487060?tenantId=5b973f99-77df-4beb-b27d-aa0c70b8482c&groupId=3f22a178-b2af-4d1a-99cd-bc1781c11210&parentMessageId=1663194560543&teamName=HCAP&channelName=General&createdTime=1663281487060&allowXTenantAccess=false