usePostActions: avoid theme fetch for non template part types

[ellatrix]

What?

A bit related to #70535, this one avoids a request for the current theme if it's not needed. It's only needed for template parts.

Why?

How?

Testing Instructions

• Go to Site Editor > Patterns > Template Parts, and check that duplication is still available.

Testing Instructions for Keyboard

Screenshots or screencast

Before	After

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: ellatrix <[email protected]>
Co-authored-by: Mamaduka <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[Mamaduka]

An interesting optimization, but I'm having trouble finding the requests for the /themes endpoint in Editors. The active themes record used by getCurrentTheme is preloaded, so unless there's some race condition, the selector shouldn't trigger the HTTP request.

P.S. Wouldn't the same unconditional resolve select above your changes already trigger a resolution?

gutenberg/packages/editor/src/dataviews/store/private-actions.ts

Lines 130 to 132 in eae3579

	const currentTheme = await registry
	.resolveSelect( coreStore )
	.getCurrentTheme();