chore: Add tests for company transfer permissions

[Rockyy174]

No description provided.

[sourcery-ai]

Hey - I've left some high level feedback:

• The permission snapshot helpers (member_people/1, guest_people/1, permission_resources/0, resource_records/2) rely heavily on hard-coded names; consider threading through IDs from the factory-generated records instead to make the tests more robust against renames and localization changes.
• The various *_access_level helpers each embed their own access lookup logic (including a custom Ecto query for resource hubs); if there is a consolidated permission API (e.g., in Access.Fetch), it would be cleaner and less fragile to use that consistently rather than duplicating access-resolution logic.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The permission snapshot helpers (`member_people/1`, `guest_people/1`, `permission_resources/0`, `resource_records/2`) rely heavily on hard-coded names; consider threading through IDs from the factory-generated records instead to make the tests more robust against renames and localization changes.
- The various `*_access_level` helpers each embed their own access lookup logic (including a custom Ecto query for resource hubs); if there is a consolidated permission API (e.g., in `Access.Fetch`), it would be cleaner and less fragile to use that consistently rather than duplicating access-resolution logic.

---

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.}