Feature/kbdev 1306 fix disease matching with subgraphs

[mathieulemieux]

Now that the ./subgraphs API route is avail., updating the get_kb_disease_matches() function to use it instead of the problematic get_term_tree() function, the same way we experimented doing with a custom similarToExtended fixed query.

Linked to issue described in KBDEV-1306.

Here are some test results:

disease	get_term_tree	similarToExtended	subgraphs
Breast Invasive Lobular Carcinoma	87	240	240
adenocarcinoma in retrorectal cystic hamartoma	10	56	56
bone cancer	1211	4823	4823
carcinoma	11598	33328	33328
cancer	16536	65034	65034

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.90%. Comparing base (597cb97) to head (dddc839).

Additional details and impacted files

@@             Coverage Diff             @@
##           develop      #73      +/-   ##
===========================================
+ Coverage    82.88%   82.90%   +0.02%     
===========================================
  Files           18       18              
  Lines         2419     2434      +15     
===========================================
+ Hits          2005     2018      +13     
- Misses         414      416       +2     

Flag	Coverage Δ
unittests	82.90% <100.00%> (+0.02%)	⬆️

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[elewis2]

Can we get a list of the matches for the top two terms in the table above, for review by CLININFO prior to release?

[mathieulemieux]

@elewis2 , I posted examples here: https://www.bcgsc.ca/jira/browse/KBDEV-1306?focusedId=2083990&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-2083990
Let me know who you yhink I should ping on it.