fix: resolve sourcery-ai newline issue in TextArea placeholder #315

[edehvictor]

Description

This PR resolves a UI rendering bug caught by the Sourcery AI automated review on the Bulk Add Members feature.

In packages/app/src/pages/ManageCollectivePage.tsx, the TextArea placeholder was using the HTML entity 
 for a newline. Because React Native does not parse HTML entities in JSX strings, this rendered the literal text 
 on the screen instead of a line break.

I updated the placeholder to use a standard template string with an actual newline (\n), ensuring it renders correctly on both mobile and web.

About #314
Related to PR #315

How Has This Been Tested?

• Ran the local development server (yarn workspace @gooddollar/app run web).
• Navigated to the "Manage Collective" page -> "Member Management" tab.
• Verified that the TextArea placeholder text successfully breaks onto a new line without showing raw HTML entities.

Checklist:

• PR title matches follow: (Feature|Bug|Chore) Task Name (Suggested title: Bug: Fix TextArea newline rendering in ManageCollectivePage)
• My code follows the style guidelines of this project
• I have followed all the instructions described in the initial task (check Definitions of Done)
• I have performed a self-review of my own code
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works (N/A - minor UI string fix)
• New and existing unit tests pass locally with my changes
• I have added reference to a related issue in the repository
• I have added a detailed description of the changes proposed in the pull request. I am as descriptive as possible, assisting reviewers as much as possible.
• @sirpy

Summary by Sourcery

Bug Fixes:

• Correct TextArea placeholder formatting so the wallet address examples break onto a new line without showing HTML entity codes.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[L03TJ3]

@edehvictor why is this done as separate PR and not as part of the original PR where the AI review came from?
should be one and the same PR

[edehvictor]

My mistake! Closing this and pushing the commit directly to PR #315.