BRD: Implement cancellation for in-progress network calls for Affiliations and Invitations

Currently, when loading affiliations or invitations, if the user changes filters or triggers a new search before the previous request completes, the previous in-progress API call continues and may resolve after the latest request.

This can cause:

- Stale data overwriting the latest results
- UI flicker or incorrect filter display
- Unnecessary API load and wasted network calls

Locate the affiliations and invitations loading entry points and inspect how their API requests update filter results. Verify the behavior when a new search starts before the previous request completes; done means earlier requests no longer produce stale results, UI flicker, or unnecessary network work.

Written by the indexing model from the issue text.