feat(FR-2183): add filtering, sorting, pagination and fix schema alignment (#6108)

Resolves #6097(FR-2183)

## How to test

- Downgrade version of esm file for testing. (`my-keypairs`)
- Go to usersettings page
- Click config button of **My Keypair Information**

## Summary

- Remove redundant `@since(version: "26.4.0")` directives from all mutations and the main query (parent component already gates on version compatibility)
- Fix Alert `message` prop to `title` (antd v6 API)
- Add `BAIGraphQLPropertyFilter` for `accessKey` and `resourcePolicy` string filters
- Add column sorting via `KeypairOrderBy` using `convertToOrderBy` helper (default: `CREATED_AT` DESC)
- Add offset-based pagination using `useBAIPaginationOptionState` with server-side `count`
- Add BAITable column settings button via `tableSettings` prop
- Preserve filter/sort state across tab switches; reset pagination on filter/tab changes
- Add `my-keypairs` feature flag to `supports()` registry in `backend.ai-client-esm.ts` (gated at 26.4.0)
- Use `baiClient?.supports('my-keypairs')` instead of `isManagerVersionCompatibleWith('26.4.0')` in `UserSettingsPage.tsx`

## Changed Files

- `react/src/components/MyKeypairManagementModal.tsx`
- `src/lib/backend.ai-client-esm.ts`
- `react/src/pages/UserSettingsPage.tsx`

## Notes

- `createdAt`/`lastUsed` datetime filters are not added because `KeypairFilter` in the current schema only supports `accessKey`, `isActive`, `isAdmin`, `resourcePolicy` fields
- `issueMyKeypair` and `updateMyKeypair` mutation return types match the current local schema; if the backend schema is updated (PR #10415), those mutations will need a follow-up update

## Verification

```
bash scripts/verify.sh
```

Author: agatha197