VideoPress: update UI/UX when the video block doesn't belong to site

[retrofox]

Fixes #

Proposed changes:

• VideoPress: update UI/UX when the video block doesn't belong to site

Other information:

• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

• Go to the block editor
• Create/edit a VideoPress video block instance that belongs to the site
• Confirm everything works as expected
• Create a new instance but using an external video (https://videopress.com/v/NGYE1Hqy)
• Confirm the side shows a Notice about it in the Details panel
• Confirm title and description are disabled
• Confirm Video frame poster is disabled
• Confirm all controls of Privacy are disabled
• Confirm the rest work as expected

Details panel	Poster	Privacy

Screen.Recording.2023-05-03.at.17.41.14.mov

[github-actions]

Are you an Automattician? You can now test your Pull Request on WordPress.com. On your sandbox, run

bin/jetpack-downloader test jetpack update/videopress-add-not-edition-allowed-notice

to get started. More details: p9dueE-5Nn-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ⚠️ All commits were linted before commit.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped.
Then, add the "[Status] Needs Team review" label and ask someone from your team review the code.
Once you’ve done so, switch to the "[Status] Needs Review" label; someone from Jetpack Crew will then review this PR and merge it to be included in the next Jetpack release.

[dhasilva]

Tests well 🚀

[fluiddot]

Hey @retrofox 👋 , based on these changes I'm wondering if we could close #29964 as the Privacy and Rating fields are disabled when those settings can't be updated. WDYT?