Refresh the user list on seat utilization page after inviting

What does this MR do and why?

Refresh the user list on seat utilizaiton page after inviting

• If the user invites someone that affects the possible seat utilization list, we should refresh that list. Currently, the sub-optimal way we do this is merely by refreshing the page like we do on the members pages. We'll do that here.

Changlog: other EE: true

Screenshots or screen recordings

Before	After
Screen_Recording_2025-03-14_at_4.09.17_PM	Screen_Recording_2025-03-14_at_4.12.16_PM

How to set up and validate locally

1. Setup gdk to simulate SaaS - https://docs.gitlab.com/ee/development/ee_features.html#simulate-a-saas-instance and restart GDK
2. create a group
3. In the gitlab admin UI, edit the group to be on an ultimate trial(admin -> groups -> edit your group)
4. In rails console, change the trial, trial start and end date for the group

   Group.last.gitlab_subscription.update_columns(trial_starts_on: Date.today, trial_ends_on: 30.days.from_now, trial: true)

5. Add a duo enterprise trial to that namespace in the rails console

n = Group.last
add_on = ::GitlabSubscriptions::AddOn.where(name: ::GitlabSubscriptions::AddOn.names[:duo_enterprise]).last
::GitlabSubscriptions::AddOnPurchase.create(add_on: add_on, namespace: n, quantity: 1, started_at: Time.current, expires_on: 30.days.from_now, purchase_xid: SecureRandom.hex(16), trial: true, organization_id: 1)

6. Go to the /groups/<your group name>/-/settings/gitlab_duo/seat_utilization page for your group and invite members from the invite banner

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #525148 (closed)