DataViews: Don't render actions dropdown when all eligible ones are primary

[ntsekouras]

What?

Related: #66811 and #67020

There can be cases where the eligible actions are all primary ones. In that case there is no need to render the dropdown with the actions as it will only contain the primary ones. This is used in table layout for now.

Testing Instructions

1. In storybook or a component that uses DataViews pass two primary actions only and choose the table layout.
2. The dropdown should not be rendered.
3. Everything else should work as before.

[github-actions]

Flaky tests detected in e5ad8ea.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/12427420451
📝 Reported issues:

• [Flaky Test] Navigates the items list via UP/DOWN arrow keys #64334 in /test/e2e/specs/site-editor/dataviews-list-layout-keyboard.spec.js
• [Flaky Test] submenu click on the arrow interactions #61884 in /test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js

[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: ntsekouras <ntsekouras@git.wordpress.org>
Co-authored-by: mcsf <mcsf@git.wordpress.org>
Co-authored-by: oandregal <oandregal@git.wordpress.org>

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

[oandregal]

Haven't tested but sounds sensible for the table layout. We can't do this for grid or list, though.