Fix saved search

[LianaHarris360]

Summary

Description of the change(s) you made

This pr fixes the issue occurring where attempting to save searches resulted in the error: Attempted to save CreatedChange change for savedsearch before setting channel_id and user_id.

This issue was fixed by adding getUserId() function to the Resource SavedSearch, using saved_by param to set user id.

This pr also adds a null check to the function searchFilterCount() within SavedSearchedModal.vue to ensure val is not null before reaching the string processing step, avoiding errors on val.split.

Manual verification steps performed

1. Sign in to studio and open an editable channel
2. Click the "Add" dropdown button and select "Import from channels"
3. Type a search term in the search field and click the "Search" button
4. Click "Save search" link

Screenshots (if applicable)

SavedSearches.mov

---

Reviewer guidance

How can a reviewer test these changes?

1. Sign in to studio and open an editable channel
2. Click the "Add" dropdown button and select "Import from channels"
3. Type a search term in the search field and click the "Search" button
4. Click "Save search" link and confirm that the search was saved

References

Fixes #4577

---

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. Manual QA checks out! Thanks @LianaHarris360