tools: More handling of no-mirror packages/test-environment

[anomiex]

Proposed changes:

In release-plugin.sh, don't wait for the package to be published to Packagist since it won't be.

In version-packages.sh, remove the package from require-dev.

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

• Try it?

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

[tbradsha]

The change in tools/release-plugin.sh is effectively what I did to bypass this on the fly and makes sense to me.

As for the change in tools/version-packages.sh, I started getting confused when looking:

• It does appear to remove automattic/jetpack-test-environment in the composer.lock in most places (but not all).
• It introduces automattic/wordbless. Is that expected?
• I also notice that a lot of dev dependencies (with mirror repos) remain versioned as @dev. Is that expected?

Finally, would it make sense to just chop dev dependencies altogether in the mirror repos? 🤔

[anomiex]

It introduces automattic/wordbless. Is that expected?

If you're just running the script, it's probably downgrading the packages to the previous release from before test-environment was added. Now that I've done a trunk merge, maybe it's a bit less confusing.

I also notice that a lot of dev dependencies (with mirror repos) remain versioned as @dev. Is that expected?

Where? In the composer.lock? That's probably because it's that way in Packagist. Why that might be I don't know.

Finally, would it make sense to just chop dev dependencies altogether in the mirror repos? 🤔

Maybe.

[anomiex]

Why that might be I don't know.

Ah, the ones that have that going on appear to be the ones using .extra.dependencies.test-only, and it's the test-only dependencies staying at @dev.