Bump tested up to version to 7.0

[phpbits]

Description of the Change

Updates tested up to version to 7.0

Closes #359

How to test the Change

Changelog Entry

Bump WordPress "tested up to" version 7.0

Credits

Props @phpbits

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added Critical Flows, Test Cases, and/or End-to-End Tests to cover my change.
• All new and existing tests pass.

[jeffpaul]

@phpbits @dkotter @peterwilsoncc looks like we can also update this as well?

simple-podcasting/assets/js/create-podcast-show.js

Lines 19 to 20 in 17287bc

	// Once WordPress 6.6 becomes our minimum, change this back to `import { PluginDocumentSettingPanel } from '@wordpress/editor';`.
	const PluginDocumentSettingPanel = wp.editor?.PluginDocumentSettingPanel ?? ( wp.editPost?.PluginDocumentSettingPanel ?? wp.editSite?.PluginDocumentSettingPanel );

[dkotter]

@phpbits @dkotter @peterwilsoncc looks like we can also update this as well?

simple-podcasting/assets/js/create-podcast-show.js

Lines 19 to 20 in 17287bc

	// Once WordPress 6.6 becomes our minimum, change this back to `import { PluginDocumentSettingPanel } from '@wordpress/editor';`.
	const PluginDocumentSettingPanel = wp.editor?.PluginDocumentSettingPanel ?? ( wp.editPost?.PluginDocumentSettingPanel ?? wp.editSite?.PluginDocumentSettingPanel );

Yep, no longer need that shim if we bump our minimum past 6.6. Likely have this in other plugins as well if I'm remembering correctly

[peterwilsoncc]

I've updated the import in 34f5314.

As we're bumping the minimum supported version of WP, this will require a release as it modifies the PHP file. I've moved the header for the minimum version in 39eb978 so we can do out of release cycle updates in the future.

[peterwilsoncc]

LGTM and tests well.

[jeffpaul]

@peterwilsoncc besides the two dependabot bump PRs, Is there anything else you'd want to get into a release here (so we can get WPORG current on tested-up-to and WP min)?

[peterwilsoncc]

@jeffpaul I've created an issue for a proposed release, see #366