[meta] Project Browser 2.0.0-alpha10

Refreshing, since we've had some advances in the last few hours.

Also making ✨ Feature: Include option in drupalorg_jsonapi source to show only locally installed modules Active a should-have, because Naren is on it and it has turned out to be very, very attainable thanks to the flexibility of the drupal.org JSON API.

Adding ✨ ModuleActivator should generate a link to a module's help if the Help module is enabled and the module implements hook_help Active to the could-have list, since I think it would be a nice enhancement. Also adding 📌 Move the Project browser specific styling from gin theme to project browser's scope. Active as a should-have so that styling issues in Gin (read: Drupal CMS) are no longer blocked by differences or upstream changes in Gin.

Just triggering a refresh - it's a rising tide of green!

✨ Allow recipes to expose additional follow-up tasks to Project Browser Active landed!

First should-have has landed! ✨ Feature: Include option in drupalorg_jsonapi source to show only locally installed modules Active

Adding 📌 Create more assertive wait methods for ProjectBrowserUiTestTrait Active and 📌 Add a more assertive waitForElementVisible() method to ProjectBrowserUiTestTrait Active as should-haves because they improve our test coverage in significant ways, and are already RTBC!

Adding 🐛 Fix flaky test: testInstallUnlockMessage Active as a should-have because it eliminates flakiness in a test, which is always valuable.

After a bit of discussion with @chrisfromredfin, I'm demoting 🐛 The Svelte code should not have custom logic for the Gin theme Active to a could-have. The more important thing is for us to become responsible with the styling, which we're doing in 📌 Move the Project browser specific styling from gin theme to project browser's scope. Active . Once we control the styling, we'll have a lot more latitude to decide which CSS classes we should or shouldn't apply in a given situation (which is why we currently need the Gin checks in the Svelte code).

Re-saving to trigger a refresh now that ✨ EnabledSourceHandler's query result caching should also consider the contents of composer.lock Active is in. Look at all that green!

Our last must-have landed: 📌 Replace install/select button with a Drupal's action button Active

But, because Gin now doesn't apply PB styling if Project Browser alpha10 or later is detected, I think I have to promote 📌 Move the Project browser specific styling from gin theme to project browser's scope. Active to a must-have.

📌 Move the Project browser specific styling from gin theme to project browser's scope. Active is in, and that is the final domino. Project Browser 2.0.0-alpha10 is on the way...

Automatically closed - issue fixed for 2 weeks with no activity.