feat(patients): add individual phenopackets endpoint w/ attachment option

[davidlougheed]

adds an endpoint that looks like /api/individuals/ind:HG00096/phenopackets to get all phenopackets for an individual, with an optional attachment=1 query param to get it with a Content-Disposition: attachment; ... header for future downloading use

[codecov]

Codecov Report

Merging #433 (0c2e60e) into develop (1b0dfed) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #433      +/-   ##
===========================================
+ Coverage    86.39%   86.42%   +0.02%     
===========================================
  Files          129      129              
  Lines         5146     5156      +10     
  Branches       680      680              
===========================================
+ Hits          4446     4456      +10     
  Misses         521      521              
  Partials       179      179              

Files Changed	Coverage Δ
chord_metadata_service/patients/api_views.py	100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[gsfk]

Is this any different from katsu /api/phenopackets/{id}? It's hard to tell exactly since our current crop of test data doesn't cover the case of multiple phenopackets per individual.

This does highlight some weirdness from the current response from /api/individuals/{id}, which includes a phenopackets array that you might guess would give the same response as the endpoint in this pr, but you'd be wrong, since it does two odd things:

• it removes all subject fields (sex, age, etc) and moves them to the top level of the response
• it copies (!) the biosamples field to the top level of the response so that all biosample and experiment data is given twice.

[noctillion]

It works as expected locally. lgtm