Add edit permission check on edit title and description icon button

[akolson]

Summary

Description of the change(s) you made

This pr prevents users with view-only permissions from editing a channel title and description.

Manual verification steps performed

• See Unstable - A user with "View-only" permissions can edit the title and description of resources and folders #4701

Screenshots (if applicable)

Before

After: Option now removed if view-only

Does this introduce any tech-debt items?

No

Reviewer guidance

How can a reviewer test these changes?

1. Create a user A, and sign in as user A
2. Create a channel and add some content.
3. Create another user B
4. Open a channel and select the 'Share channel' option
5. Share the channel with user B by selecting the Can view option
6. The Edit title and description icon next to the resources and folders should not be visible

References

Fixes #4701

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

[AlexVelezLl]

Thanks @akolson!! LGTM!

[pcenov]

Great @akolson - I also confirm that #4701 is fixed!