Scripts: Avoid tests getting published to npm

[manzoorwanijk]

Follow up of #79095 (comment)

What?

Currently, the script package publishes test files to npm, which it ideally shouldn't.

Why?

The test files are not meant for npm.

How?

• Add a negation for test directory to skip it for publishing
• Move rimraf to dev deps

Testing Instructions

• cd packages/scripts && npm pack
• Unpack the tarbal
• Verify that the test directory is not included.

Testing Instructions for Keyboard

Screenshots or screencast

Before	After

Use of AI Tools

[github-actions]

Size Change: 0 B

Total Size: 8.58 MB

_{compressed-size-action}

[github-actions]

Flaky tests detected in 8d9c15a.
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/27564964996
📝 Reported issues:

• [Flaky Test] should update the HTML only for the latest navigation #78835 in /test/e2e/specs/interactivity/router-navigate.spec.ts

[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: manzoorwanijk <manzoorwanijk@git.wordpress.org>
Co-authored-by: aduth <aduth@git.wordpress.org>

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