Add Jetpack Boost plugin

[gravityrail]

This is part of our work to support easier sharing of design elements via Jetpack RNA and in generate to improve collaboration between Jetpack ecosystem plugins, as well as making it easier to onboard Jetpack developers.

Changes proposed in this Pull Request:

• Add Jetpack Boost to the Jetpack monorepo

Jetpack product discussion

TODO

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

No

Testing instructions:

TODO

[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.
  
• ✅ All commits were linted before commit.
  
• 🔴 Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ 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.

---

Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped.
Then, add the "[Status] Needs Team review" label and ask someone from your team review the code.
Once you’ve done so, switch to the "[Status] Needs Review" label; someone from Jetpack Crew will then review this PR and merge it to be included in the next Jetpack release.

---

Boost plugin:

• Next scheduled release: August 3, 2021.
• Scheduled code freeze: July 26, 2021.

[anomiex]

Gave the structure of it a once-over. A lot of it is identifying things that can probably be deleted.

I note you didn't import any history of the old repo. Just confirming, was that intentional?

[anomiex]

I don't think this file is needed. We don't use wp dist-archive to create the plugin zip.

But you'll probably want to look at this file for ideas on what you need to tag with "production-include" and "production-exclude" in .gitattributes:

• Anything listed here that's not already in .gitignore (and doesn't get deleted with the move to the monorepo) should get "production-exclude".
• Anything that's in .gitignore but not in this file should get "production-include". Most notably, you'll want to look at the production-include rules that the other plugins use to get stuff from vendor/ included in the plugin zip.

P.S. Once you get the Build workflow passing, you can see the would-be contents of the plugin zip in the "jetpack-build" artifact produced by that workflow.

[anomiex]

What's this file for?

[anomiex]

Everything in projects/plugins/jetpack-boost/.github/ should probably be deleted. We generally configure the mirror repo to not allow issues in the first place, and to auto-close PRs with a pointer to the monorepo. Similarly, tools like renovate and stale are run in the monorepo rather than the mirror.

[kraftbj]

Deleted most of it, but left the things that we may still want to pull things from for now. 20530e1

[anomiex]

This one might be worth moving into the monorepo's .github/workflows/. Unfortunately we don't have any infrastructure yet for running E2E tests.

[gravityrail]

@anomiex

I note you didn't import any history of the old repo. Just confirming, was that intentional?

Yes

[thingalon]

Wow, thank you for handling the complex work of merging all the things, @kraftbj, @gravityrail and @anomiex!