🐛 HTTPException -> JSONResponse: fix exception handler in api-server

[bisgaard-itis]

What do these changes do?

• I recently introduced a more comprehensive exception handling in the api-server. However I learned that Starlette catches my HTTPExceptions and returns them to the client with status code 500 because I should be using JSONResponse instead.
• This fixes this issue.

Related issue/s

• resolves Fix exception handler in api server #5384

How to test

Dev Checklist

• No ENV changes or I properly updated ENV (read the instruction)

DevOps Checklist

[codecov]

Codecov Report

Attention: Patch coverage is 66.66667% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 65.7%. Comparing base (194830a) to head (7a5b356).

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #5385      +/-   ##
=========================================
- Coverage    87.5%   65.7%   -21.8%     
=========================================
  Files        1322     613     -709     
  Lines       54221   29878   -24343     
  Branches     1174     203     -971     
=========================================
- Hits        47465   19647   -27818     
- Misses       6507   10180    +3673     
+ Partials      249      51     -198     

Flag	Coverage Δ
integrationtests	63.9% <ø> (-1.3%)	⬇️
unittests	84.5% <66.6%> (-0.9%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
...ervice_api_server/api/errors/httpx_client_error.py	43.7% <66.6%> (+3.7%)	⬆️

... and 1055 files with indirect coverage changes

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud