Update node details query to use CTE and more robust tests

[bjester]

Summary

Description of the change(s) you made

• Updates the query that's used for validating the cache when querying a node's details
• No change in behavior was intended (even though there are lots of questions about this code Channel details - The channel info is not getting updated correctly #4123)
• Adds more robust tests to verify all scenarios of affected code
• Also adds some explicit analytics since the URL fragment for the frontend details view is not available in GA

Manual verification steps performed

1. Created regression tests
2. Verified new tests passed
3. Implemented changes
4. Verified tests passed
5. Updated tests and some logic further to simplify some queries, like repeated queries for the channel object

---

Reviewer guidance

How can a reviewer test these changes?

• Can you load the channel details?

Are there any risky areas that deserve extra testing?

• Do the tests make sense?

References

Fixes #4795

Comments

---

Contributor's Checklist

PR process:

• If this is an important user-facing change, PR or related issue the CHANGELOG label been added to this PR. Note: items with this label will be added to the CHANGELOG at a later time
• If this includes an internal dependency change, a link to the diff is provided
• The docs label has been added if this introduces a change that needs to be updated in the user docs?
• If any Python requirements have changed, the updated requirements.txt files also included in this PR
• Opportunities for using Google Analytics here are noted
• Migrations are safe for a large db

Studio-specifc:

• All user-facing strings are translated properly
• The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)
• All UI components are LTR and RTL compliant
• Views are organized into pages, components, and layouts directories as described in the docs
• Users' storage used is recalculated properly on any changes to main tree files
• If there new ways this uses user data that needs to be factored into our Privacy Policy, it has been noted.

Testing:

• Code is clean and well-commented
• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical user journeys are covered by Gherkin stories
• Any new interactions have been added to the QA Sheet
• Critical and brittle code paths are covered by unit tests

---

Reviewer's Checklist

This section is for reviewers to fill out.

• Automated test coverage is satisfactory
• PR is fully functional
• PR has been tested for accessibility regressions
• External dependency files were updated if necessary (yarn and pip)
• Documentation is updated
• Contributor is in AUTHORS.md

[sentry-io]

🔍 Existing Issues For Review

Your pull request is modifying functions with the following pre-existing issues:

📄 File: contentcuration/contentcuration/models.py

Function	Unhandled Issue
get_details	TypeError: 'NoneType' object is not iterable /api... Event Count: 22

📄 File: contentcuration/contentcuration/views/nodes.py (Click to Expand)

Function	Unhandled Issue
get_channel_details	TypeError: 'NoneType' object is not iterable /api... Event Count: 22

---

_{Did you find this useful? React with a 👍 or 👎}

[rtibbles]

Test cases look like good coverage and inspire confidence (and all pass)! No regressions spotted in manual testing.

[rtibbles]

👍

[rtibbles]

I really think not!

[pcenov]

No regressions observed while viewing the channel details.