fix: Use correct env. ID when listing groups in a project

[spaceemotion]

Problem

Closes #29099

Changes

Using a debugger I was able to trace back which ID should be the correct one. For the changes, I used a different frontend file as guidance:

posthog/frontend/src/scenes/pipeline/overviewLogic.tsx

Line 14 in 3878c90

['currentTeamId'],

Does this work well for both Cloud and self-hosted?

No impact.

How did you test this code?

No tests have been made as I don't have a local PostHog installation.

[greptile-apps]

PR Summary

This PR fixes a critical issue where groups were not appearing in environments by correcting the ID used for API calls in the groups list feature.

• Changed import from projectLogic to teamLogic in /frontend/src/scenes/groups/groupsListLogic.ts
• Replaced currentProjectId with currentTeamId for API calls to properly handle environment-specific group listings
• Fix aligns with existing implementation pattern seen in pipeline overview logic

_{💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!}

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}