Cursor: Add API reuse and code pattern guidelines to development documentation

[lezama]

Proposed changes:

• Added new "API and Package Reuse" section to encourage better code reuse practices
  • Package assessment guidelines
  • Reuse strategy recommendations
  • Integration guidelines
  • Performance considerations
• Added new "Code Patterns and Readability" section to improve code consistency
  • Pattern consistency guidelines
  • Pull request clarity standards
  • Code organization best practices
  • Documentation alignment requirements
• Enhanced existing development guidelines to promote:
  • More efficient code reuse across the monorepo
  • Consistent development patterns
  • Better PR readability
  • Clearer documentation standards

Testing instructions:

• Generally to use it in Cursor.

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

No.

[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.
  
• 🔴 Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ 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.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

[jeherve]

I like the idea of pushing for leveraging existing things instead of reinventing the wheel! 👍