feature request: pagination and filtering support in invitation api

[terion-name]

What problem did you meet?

it's a known (#5934) limitation, but it is very strange (why not all resources support pagination as standart?) and very problematic, because invites are not deleted, the accept end expire, but stay and build up. And pulling hundreds of them to show in ui is not good performance-wise

Describe what you'd like Logto to have

apply standart pagination and filtering to all resources, limitations included

[xiaoyijun]

Hi @charIeszhao , could you please take some time to have a look when you're available?

[charIeszhao]

Yes, this is an acknowledged limitation.

As we first implement the invitation feature in Console, it was considered to be a lower frequency activity, as there are usually no more than 10 seats in any tenant.

Therefore, due to the limited time frame and the reason above, we implemented the initial version of it, without the pagination.

Can you let us know your use case, why would it be "hundreds of them" in your tenant? I'm a bit curious because usually you don't have those many records if you don't abuse the feature.