Support split bounty payouts across multiple PR wallet tags

[yahweh982]

Fixes #12

Summary:

• Parse every hidden bountic-address tag in the winning PR body instead of only one address.
• Split the bounty amount evenly to cents across wallet recipients.
• Persist one payout_events row per recipient and include recipient details in bounty activity metadata.
• Keep the existing single-recipient response fields for backward compatibility while adding a recipients array.

Supported wallet tag examples:

<!-- bountic-address: 0x1111111111111111111111111111111111111111 -->
<!-- bountic-address: @alice 0x2222222222222222222222222222222222222222 -->
<!-- bountic-address: bob=0x3333333333333333333333333333333333333333 -->

Validation:

• ./node_modules/.bin/tsc --noEmit
• ./node_modules/.bin/eslint lib/bounty/services/payout.ts lib/bounty/services/approve-payout.ts
• git diff --check

[vercel]

@yahweh982 is attempting to deploy a commit to the skndash96's projects Team on Vercel.

A member of the Team first needs to authorize it.

[bountic-bot]

⚡️ Bounty Competition Started

@yahweh982 has submitted a PR that references an issue with a bounty. Learn more about this bounty: https://bountic.vercel.app/b/skndash96/bountic/issues/12

When this PR is merged, the bounty will be locked and ready for payout approval.

---

Bountic: Autonomous USDC bounties for open source

[yahweh982]

Maintainer note: the failing Vercel check appears to be the Vercel team deployment authorization gate (Authorization required to deploy), not a code/test failure.

Local validation passed before opening this PR:

• ./node_modules/.bin/tsc --noEmit
• ./node_modules/.bin/eslint lib/bounty/services/payout.ts lib/bounty/services/approve-payout.ts
• git diff --check

GitHub also reports no conflicts with the base branch. Happy to adjust the recipient parsing format if you prefer a different wallet tag convention.