Related PRs:

• Refactor the logic to fetch metadata of VideoPress videos WordPressKit-iOS#581
• Bump minimum version of WordPressKit dependency to 7.0 WordPressAuthenticator-iOS#754

Fixes #20195

This PR updates the logic to fetch VideoPress metadata and the usage of VideoPress videos.

To test

Media screen

Preparation:
As we need to test with a video, first we need to upload it. This is recommended to be done in the browser to ensure that the video points to a remote URL instead of a local cache version.

1. Go to a simple site in the browser.
2. Go to the Media page.
3. Upload a video.

NOTE: By default, the privacy of the video will be Site Default.

1 - Public site

To set the site public:

1. Go to the Site Settings screen.
2. Tap on the Privacy option.
3. Change privacy to Public or Hidden.

1.1 - Public video

1. Go to a simple site in the browser.
2. Go to the Media page.
3. Edit the uploaded video.
4. Change Privacy to Public
5. Open the app.
6. Go to the Media screen.
7. Tap on the uploaded video.
8. Play the video.
9. Observe that the video can be played.

1.2 - Private video

1. Go to a simple site in the browser.
2. Go to the Media page.
3. Edit the uploaded video.
4. Change Privacy to Private
5. Open the app.
6. Go to the Media screen.
7. Tap on the uploaded video.
8. Play the video.
9. Observe that the video can be played.

1.3 - Site default video

1. Go to a simple site in the browser.
2. Go to the Media page.
3. Edit the uploaded video.
4. Change Privacy to Site Default
   NOTE: The privacy will be the same as the site, i.e. Public.
5. Open the app.
6. Go to the Media screen.
7. Tap on the uploaded video.
8. Play the video.
9. Observe that the video can be played.

2 - Private site

To set the site public:

1. Go to the Site Settings screen.
2. Tap on the Privacy option.
3. Change privacy to Private.

2.1 - Public video

Repeat the same steps as on the public site (1.1).

2.2 - Private video

Repeat the same steps as on the public site (1.2).

2.3 - Site default video

Repeat the same steps as on the public site (1.3).

Story post

1. Create a Story post.
2. Open the media selection sheet by tapping on the square icon on the left side.
3. Tap on the Media tab.
4. Select an uploaded video that is private.
5. Observe that the video is added to the story.

Classic editor (Aztec)

1. Create a post.
2. Switch to HTML mode by tapping on the three dots icon located at the top bar.
3. Type some text without HTML tags (e.g. This is the classic editor.).
4. Save the post and open it again.
5. Observe that the post is opened with the classic editor.
6. Tap on the ➕ button located in the bottom bar.
7. Tap on the WordPress icon to display the items of the Media library.
8. Select an uploaded video that is private.
9. Observe that the video is added to the post.
10. Tap on the video and play it.
11. Observe that the video is played.

NOTE: The video's poster seems to disappear randomly. This doesn't look like a regression as I managed to reproduce it in previous versions. As far as I investigated, this is caused by how the video element is coded in the Classic editor when using a VideoPress video.

Gutenberg editor

Simple site

NOTE: Private videos won't be displayed in the editor (wordpress-mobile/gutenberg-mobile#5497), so it's recommended to use a public/hidden Simple site.

Video upload within the editor

1. Create a post.
2. Tap on the ➕ button and add a Video block.
3. Tap on the "Choose from device" option.
4. Select a video file.
5. Wait until the upload finish.
6. Observe that the video is added to the block and that can be played.
7. Switch to HTML mode.
8. Observe that the video source points to VideoPress (e.g. https://videos.files.wordpress.com/<VIDEO_ID>/<FILENAME>)

Video upload outside the editor

1. Create a post.
2. Tap on the ➕ button and add a Video block.
3. Tap on the "Choose from device" option.
4. Select a video file.
5. Before the upload finish, tap on the ❌ button to close the editor and save the post.
6. In the Post list, wait until the upload finish.
7. Open the same post.
8. Observe that the video is added to the block and that can be played.
9. Switch to HTML mode.
10. Observe that the video source points to VideoPress (e.g. https://videos.files.wordpress.com/<VIDEO_ID>/<FILENAME>)

Self-hosted site with Jetpack

NOTE: Free users can only have one video in VideoPress, so keep this in mind when testing. In case you already uploaded a video, you can delete it and upload a new one (navigate to https://<SITE_HOST>/wp-admin/admin.php?page=jetpack-videopress#/). Alternatively, you can purchase the VideoPress plan to have unlimited uploads.

Video upload within the editor

1. Repeat the same steps as in Simple site - Video upload within the editor.

Video upload outside the editor

1. Repeat the same steps as in Simple site - Video upload outside the editor.

Self-hosted site without Jetpack

Video upload within the editor

1. Repeat the same steps as in Simple site - Video upload within the editor.
2. When switching to HTML mode, observe that the video URL points to the site instead of Video Press (i.e. https://<SITE>/wp-content/uploads/2023/03/<FILENAME>)

Video upload outside the editor

1. Repeat the same steps as in Simple site - Video upload outside the editor.
2. When switching to HTML mode, observe that the video URL points to the site instead of Video Press (i.e. https://<SITE>/wp-content/uploads/2023/03/<FILENAME>)

Regression Notes

1. Potential unintended areas of impact
   I haven't identified unintended areas of impact apart from the ones outlined in the above test cases.

2. What I did to test those areas of impact (or what existing automated tests I relied on)
   N/A

3. What automated tests I added (or what prevented me from doing so)
   I'm planning to create a follow-up PR to include automated tests.

PR submission checklist:

• I have completed the Regression Notes.
• I have considered adding unit tests for my changes.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.