Export seat usage as CSV

What does this MR do?

This MR adds ability for top-level group owners to export seat usage data as CSV file. This new feature is behind the seat_usage_export feature flag.

The CSV is streamed as request response, same as what we do when exporting users for self-managed instances. Before we enable the feature flag globally we should test with some groups that have many billable members.

There are couple of changes not directly related to the export feature, but made to match what we do in the API endpoint when listing the same data on the page:

1. check if group is top-level group.
2. use same policy (admin_group_member instead of admin_group)

Related to #262877 (closed).

Screenshots or Screencasts (strongly suggested)

How to setup and validate locally (strongly suggested)

Example below:

1. Enable seat usage export

   Feature.enable(:seat_usage_export)

2. With CustomersDot up and running, go to Settings -> Billing -> Seat usage for a group that has a subscription.
3. Click Export list.

Does this MR meet the acceptance criteria?

Conformity

• I have included changelog trailers, or none are needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.
• This change is backwards compatible across updates, or this does not apply.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)
• I have tested this MR in all supported browsers, or it's not needed.
• I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Related to #262877 (closed)