Properly format node_id+channel_id query parameter

[bjester]

Summary

Description of the change(s) you made

• Updates resource method getByNodeIdChannelId to use proper format for the query parameter
• Updates other potential issues related to [node_id+channel_id]__in filtering

Manual verification steps performed

1. Create public channel with some nodes and publish it
2. Sign out
3. Sign into Studio
4. Create new channel (without opening the public channel)
5. Click ADD and select 'Import from channels'
6. Search for one of the public channel nodes
7. Click the clipboard icon on the node

---

Reviewer guidance

How can a reviewer test these changes?

Follow the above steps

Are there any risky areas that deserve extra testing?

I did update some clipboard actions that seemed to be passing a flattened array for __in query

References

Fixes #4508

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

[akolson]

Changes look correct to me and clipboard action works as expected. Thanks @bjester

[AlexVelezLl]

Looks good to me, I runned the code and confirmed that now clipboard is working fine!

[rtibbles]

I opened this PR, nodded sagely, and thought "this makes sense", then forgot to leave a review, so I'll pile on here!

[bjester]

Thanks all!