fix: fallback group node on extractCommunityMetadata

[josecleiton]

Use group node as a fallback to fetch community metadata, preventing to access undefined

[whiskeysockets-bot]

Thanks for opening this pull request and contributing to the project!

The next step is for the maintainers to review your changes. If everything looks good, it will be approved and merged into the main branch.

In the meantime, anyone in the community is encouraged to test this pull request and provide feedback.

✅ How to confirm it works

If you’ve tested this PR, please comment below with:

Tested and working ✅

This helps us speed up the review and merge process.

📦 To test this PR locally:

# NPM
npm install @whiskeysockets/baileys@josecleiton/Baileys#master

# Yarn (v2+)
yarn add @whiskeysockets/baileys@josecleiton/Baileys#master

# PNPM
pnpm add @whiskeysockets/baileys@josecleiton/Baileys#master

If you encounter any issues or have feedback, feel free to comment as well.

[josecleiton]

Before this change, methods such as communityUpdateDescription that rely on communityMetadata failed.

const communityId = community.attrs.id?.includes('@')
                                  ^

TypeError: Cannot read properties of undefined (reading 'attrs')
    at extractCommunityMetadata (/app/node_modules/baileys/src/Socket/communities.ts:444:32)
    ```

[github-actions]

This PR is stale because it has been open for 14 days with no activity. Remove the stale label or comment or this will be closed in 14 days