Fix for not retrieving all items when response has multiple pages of items

[renoyjohnm]

This pull request includes significant changes to the get_items_by_name function in tabcmd/commands/server.py to support pagination and improve item retrieval. Additionally, comprehensive unit tests have been added to ensure the function's correctness under various scenarios.

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
tabcmd
__main__.py	10	10	10	0%
tabcmd.py	14	14	14	0%
version.py	6	3	3	50%
tabcmd/commands
commands.py	10	10	10	0%
constants.py	77	15	15	81%
server.py	133	19	19	86%
tabcmd/commands/auth
session.py	360	42	42	88%
tabcmd/commands/datasources_and_workbooks
datasources_and_workbooks_command.py	127	16	16	87%
datasources_workbooks_views_url_parser.py	140	10	10	93%
delete_command.py	60	16	16	73%
export_command.py	114	25	25	78%
get_url_command.py	127	47	47	63%
publish_command.py	82	24	24	71%
runschedule_command.py	21	7	7	67%
tabcmd/commands/extracts
create_extracts_command.py	42	8	8	81%
decrypt_extracts_command.py	27	2	2	93%
delete_extracts_command.py	37	6	6	84%
encrypt_extracts_command.py	27	2	2	93%
extracts.py	20	2	2	90%
reencrypt_extracts_command.py	27	2	2	93%
refresh_extracts_command.py	48	13	13	73%
tabcmd/commands/group
create_group_command.py	29	5	5	83%
delete_group_command.py	27	2	2	93%
tabcmd/commands/project
create_project_command.py	46	8	8	83%
delete_project_command.py	35	4	4	89%
publish_samples_command.py	30	4	4	87%
tabcmd/commands/site
create_site_command.py	34	5	5	85%
delete_site_command.py	28	2	2	93%
edit_site_command.py	38	2	2	95%
list_command.py	44	10	10	77%
list_sites_command.py	29	2	2	93%
tabcmd/commands/user
create_site_users.py	57	10	10	82%
create_users_command.py	60	10	10	83%
delete_site_users_command.py	43	5	5	88%
user_data.py	221	31	31	86%
tabcmd/execution
_version.py	2	2	2	0%
global_options.py	145	23	23	84%
localize.py	69	11	11	84%
logger_config.py	42	6	6	86%
tabcmd_controller.py	41	6	6	85%
TOTAL	2707	441	84%

[jacalata]

Some sites have thousands of items. What's the performance going to be like in that case?

[renoyjohnm]

Some sites have thousands of items. What's the performance going to be like in that case?

This issue is specifically is about fetching all items filtered to the provided item name & doesn't fetch all items of a content type from the site. Yes, there could be multiple pages of items with the same name (like in the case of customer issue) & could be low of occurrence given the filter query but I believe we should be fetching all the results from the multiple pages of items despite the performance hit instead of just relying on the first page of items which could lead to unintended consequences. Please let me know of your thoughts on it, Thanks

[jacalata]

The point of the bug is that we want to return more than the first page, yes. But what is the performance like? Does it appear to hang?

[renoyjohnm]

The point of the bug is that we want to return more than the first page, yes. But what is the performance like? Does it appear to hang?

Not much in the limited testing I performed but it could, depending on the network latency for the requests, another quick option be to bump the default value of TSC_PAGE_SIZE to 500 to reduce the number of API calls for fetching all the pages of items, thoughts?

[jacalata]

that does sound like a great quick fix. We could do that and then take a bit more time on this one.