NickAkhmetov/CAT-844 Migrate away from using `descendants` and `ancestors` in favor of `id` equivalents

[NickAkhmetov]

Summary

This PR removes the portal UI's dependencies on the direct ancestor/descendant information available in the entity API in favor of using the corresponding ids.

Progress

• ancestors
  • [x] Dev search used ancestors to determine raw/processed status -> revised to use processing field
  • [x] Prov table used ancestors to construct the table -> revised to use ancestor_ids, corresponding revisions made to error display for donors
  • [x] Ancestors' rui_location field is used for details_rui_json on back-end and to determine whether a dataset is spatial in the dev search
  • [x] Ancestors not being datasets is currently a condition for the unified prov view lookup when looking up the top level dataset -> dropped the condition in favor of using processing: raw, there should be 0..1 raw datasets in any given dataset's ancestors anyway.
• descendants
  • Not in use.
• immediate_ancestors
  • Mentioned in an artillery config, but otherwise not present.
• immediate_descendants
  • useImmediateDescendantProv is used for the view derived entities button This actually uses the entity API endpoint; this can be improved to use the search API equivalent once the upstream change is made to the search API, but is not currently a blocker.

Design Documentation/Original Tickets

https://hms-dbmi.atlassian.net/browse/CAT-844

Testing

Manually verified, confirmed functionality is analogous to current production behaviors.

Screenshots/Video

Not very informative since this matches existing functionality, but for verification:

Dev search filters

  

Checklist

• [x] Code follows the project's coding standards
  • [x] Lint checks pass locally
  • [x] New CHANGELOG-your-feature-name-here.md is present in the root directory, describing the change(s) in full sentences.
• [x] Unit tests covering the new feature have been added
• [x] All existing tests pass
• [x] Any relevant documentation in JIRA/Confluence has been updated to reflect the new feature
• [x] Any new functionalities have appropriate analytics functionalities added