[BUG] FLytectl pagination should use server returned token instead of page number

[pmahindrakar-oss]

Describe the bug

Currently flytectl computes the token using Page number and limit provided by the user from the commandline

https://github.com/flyteorg/flytectl/blob/64d399291fb6ed326c867eb5258fbf68de75f8ca/pkg/filters/util.go#L61

This will cause issues if the token implementation changes in flyteadmin.

Instead flytectl should rely on the token returned in the ListResponse for flyte entities and have the user pass it directly for fetching next set of results.

Expected behavior

• flytectl get launchplans/worflows/tasks/projects --filter.limit

O/p : Use the --filter.token server-returned-token to fetch the next set of results

• flytectl get launchplans/worflows/tasks/projects --token server-returned-token-from-previous-query --filter.limit

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

• [X] Yes

Have you read the Code of Conduct?

• [X] Yes

[github-actions[bot]]

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏

[github-actions[bot]]

Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏