[spsiddarthan]

Jetpack Social's paid features are broken on the trunk branch currently. When you don't have a paid plan, the upgrade nudges don't show up. Along with that, the initial state of the plugin isn't set up correctly. This was inadvertently introduced in #29910 through this bit of code https://github.com/Automattic/jetpack/blob/trunk/projects/plugins/social/src/class-jetpack-social.php#L361-L372, which overrides the initial state in https://github.com/Automattic/jetpack/blob/trunk/projects/plugins/social/src/class-jetpack-social.php#L316.

This is the PR which originally added the review prompts. But this line sets the state for the Social plugin only if the Jetpack plugin is not active which leads to #29910 being created, I presume. That accidentally stomped over the plugin's initial state.

I am not entirely sure how to go about fixing the review prompts when both the plugins are active, requires a bit of thinking I would reckon, but to restore the plugin to a working state I have the code that enqueues the review prompt-related script. I wonder if we can revert #29910 to reinstate the user reviews at least in the case where only the social plugin is active.

Proposed changes:

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:

• Remove any paid plans on your test site and boot up your Jetpack Site on trunk. You won't see the upgrade nudge for Jetpack Social in the sidebar.

• Switch to this branch and you will see that the nudge shows up.

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

---

Social plugin:

• Next scheduled release: May 2, 2023.
• Scheduled code freeze: April 24, 2023.