RAS-1290 Add clean get respondent by party_id endpoint to party service

[LJBabbage]

What and why?

This Pr adds a new endpoint to get respondents by party_id. This card is part of bigger piece to removed the business associations currently returning from the respondents by id endpoint

How to test?

Deploy this PR and run the acceptance tests (or add a respondent) make sure when you call the endpoint you get the right response. Don't forget to include basic auth details

Jira

[arroyoAle]

Looks good and tested - everything returns properly and error handling works

[pricem14pc]

/deploy pricem

[ras-rm-pr-bot]

Deploying to dev cluster with following parameters:

• namespace: pricem

• tag: pr-437

• configBranch: main

• paramKey: ``

• paramValue: ``

[pricem14pc]

As intended, SQLAlchemy query is nice and clean 👍

SELECT 
partysvc.respondent.id AS partysvc_respondent_id,
 ...
 ...
partysvc.respondent.password_reset_counter AS partysvc_respondent_password_reset_counter
FROM partysvc.respondent
WHERE partysvc.respondent.party_uuid = 'b90478a4-0eb6-4f8c-865a-d5f2df7d09ff'::UUID
LIMIT 1

[pricem14pc]

Is it worth adding in the openapi spec that the existing overloaded method is deprecated?