My Jetpack: Update filesystem check

[leogermani]

Reconstructed after #24780

Fixes #22982

This PR explores how to handle the situations in which we are not able to automatically install a plugin for the user.

The proposal is to:

• Disable the button
• Add a notice above the button with a link to the plugin on the .org repository

Another option I considered was to use the Notice core component, but it didn't fit in very well on a first try:

What do you think?

Changes proposed in this Pull Request:

• Display an alert when we can't install the plugin for the user

Jetpack product discussion

1202184803119163-as-1202324040023250

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

No

Testing instructions:

Easiest way to test this PR is by modifying the class-initializer.php file inside the my-jetpack package folder, on line 151 and make it read like:

'fileSystemWriteAccess' => 'no',

• Go to My Jetpack
• Click on "Add CRM" (or any other card for which you don't have the plugin installed

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1202324040023250

[matticbot]

Caution: This PR has changes that must be merged to WordPress.com
Hello leogermani! These changes need to be synced to WordPress.com - If you 're an a11n, please commandeer and confirm D83381-code works as expected before merging this PR. Once this PR is merged, please commit the changes to WP.com. Thank you!
This revision will be updated with each commit to this PR

[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.

[oskosk]

Tests well!

[github-actions]

Great news! One last step: head over to your WordPress.com diff, D83381-code, and deploy it.
Once you've done so, come back to this PR and add a comment with your SVN changeset ID (e.g. r12345-wpcom).

Thank you!

[leogermani]

r248257-wpcom