Dev CLI: Add mirror repo information

[kraftbj]

Adds a mirror repo so automattic/jetpack-cli will populate.

Secret has already been added.

Proposed changes:

• Adding the mirror repo information in anticipation of 1.0.

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

None yet :)

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

No.

Testing instructions:

• Does the project structure linting happy?
• Post-merge, did it work?

[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 PR itself looks fine. My main concern is one of naming...the package name here confusing, as it has historically referred to the jetpack command:

https://developer.jetpack.com/docs/jetpack-development/jetpack-cli/

I'd prefer something like jpdocker or jpdev, though I'm late to the party.

One small non-blocking nitpick if we go with this naming...I prefer the label to by "Jetpack CLI" instead of "Jetpack Cli".

[kraftbj]

@tbradsha I renamed the label. IIRC, the garending action will create it if it isn't found (what happened here), but it is case agnostic... so renaming it to Jetpack CLI should persist.

I hear you on naming. I'm also okay deferring. I don't know if this new jp option will solve the right problems and it could be that the existing jetpack becomes part of it (at least in how you use it, if not in code).

[tbradsha]

👍