[Bloganuary] Create Bloganuary Nudge FF

[thomashorta]

Part of #19663

---

To Test:

Not much to test so far (just created the FF but not being used), only check if the appropriate flag exists in the debug menu: bloganuary_dashboard_nudge and it's defaulted to OFF.

---

Regression Notes

1. Potential unintended areas of impact

   • N/A

2. What I did to test those areas of impact (or what existing automated tests I relied on)

   • N/A

3. What automated tests I added (or what prevented me from doing so)

   • N/A

---

PR Submission Checklist:

• I have completed the Regression Notes.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.

	App Name	Jetpack
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr19664-1836b2b
	Commit	1836b2b
	Direct Download	jetpack-prototype-build-pr19664-1836b2b.apk

Note: Google Login is not supported on these builds.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.

	App Name	WordPress
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr19664-1836b2b
	Commit	1836b2b
	Direct Download	wordpress-prototype-build-pr19664-1836b2b.apk

Note: Google Login is not supported on these builds.

[RenanLukas]

Thanks for the PR, LGTM

I've left a question but if it doesn't make sense feel free to merge it

[RenanLukas]

💡 Would it make sense to have the default value as true in case this is being merged directly in the new version's branch?

[thomashorta]

Ideally the FF should default to true only after all Bloganuary changes are merged, to avoid a state where we have partial changes with the flag ON.

But now that you mentioned it, since we will need to target the beta release branch directly, it might make more sense to target a feature branch, and have this flag ON, so we can then only merge 1 PR to the release branch and avoid any incomplete code or multiple PRs targeting release. I will target feature/bloganuary-nudge and default this FF to ON.

[peril-wordpress-mobile]

	Warnings
⚠️	This PR is assigned to a milestone which is closing in less than 4 days Please, make sure to get it merged by then or assign it to a later expiring milestone

Generated by 🚫 dangerJS

[wpmobilebot]

	2 Warnings
⚠️	Class BloganuaryNudgeFeatureConfig is missing tests, but unit-tests-exemption label was set to ignore this.
⚠️	This PR is assigned to the milestone 23.8. The due date for this milestone has already passed. Please make sure to get it merged by then or assign it to a milestone with a later deadline.

Generated by 🚫 Danger