Update CancerStudy with imaging sample counts

[gblaih]

Update CancerStudy type with field resourceCounts that holds resource information and counts within study and dynamically calculate these resource counts

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dippindots]

@gblaih Thanks for making efforts and making this aviablable! This is great!

Just one quick comment: I think we can go ahead and merge this as a solid initial approach. That said, we should also explore ways to automatically discover new resource types. For example, if we add a new imaging type like new_image_type, it would be ideal for it to appear on the homepage automatically. Even if this requires introducing a new endpoint or doing some additional refactoring, I believe it's worth the effort.

[dippindots]

@gblaih Overall, the PR looks great and works well for demo purposes. My comments are mainly focused on improving code clarity and aligning better with API design principles. Here's a breakdown:

• Rename resources to resourceCounts
  To better reflect the data type (List<ResourceCount>), let's rename related variables and methods in the model, service, and repository layers. (Apologies for initially suggesting resources — your original ResourceCount naming is actually more descriptive.)

• Conditionally include resourceCounts based on projection
  Since projection controls the response detail in our API, we should include resourceCounts only when projection is SUMMARY or DETAILED. We can handle this with a simple conditional in the service layer.

• Add support in fetchStudies
fetchStudies is the third method that needs to add resourceCounts, but it’s currently missing from the implementation.

• Remove hard‑coded CHROMOSCOPE and FIGURES
  Let’s avoid hardcoding these in the backend. Instead, handle them in the frontend—either by hardcoding there or by leveraging the new JSON field.

[dippindots]

Your updates looks great! I just have two more comments related to the mapper file

[dippindots]

All looks good to me! Thanks!

[dippindots]

@gblaih The tests are indicating an real issue, I have some explainations in comments

[dippindots]

I found the issue:
need to replace this with

cs.CANCER_STUDY_IDENTIFIER IN

The reason is when you give a table an alias (e.g. cancer_study cs), that alias cs replaces the original table name in the rest of the query. Using the full table name afterward will cause an error

[dippindots]

same here

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
29.6% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud