request help: Apisix ingress controller not able to sync the config for either large num of apis and admin config or with large number of paths in single route

### Issue description

Hi Team ,
We are using apisix ingress controller and apisix gateway , where we are using apisix crd with apisixupstream , apisixroute , and pluginconfig

we were deploying mutiple apis where we are creating one apisixroute per api with mutiple paths init , and we are having apis arround 700 .

In one segment the with One apisixroute with mutiple paths the deployment and validation were successfull since it was having only 100 apis .

But in this another segment we are having 700 apis and in few apis the paths are arround 150 and being added in one apisixroute so here we were getting the error as -

2026-06-05T15:35:48.086Z  ERROR  status.updater  status/updater.go:94  unable to update status  {"name": "insightvm-apis", "namespace": "apis-ns", "error": "ApisixRoute.apisix.apache.org \"insightvm-apis\" is invalid: status.conditions[0].message: Too long: may not be more than 32768 bytes"}

SO we made the change to apisixrote as for each path we will create a separate apisixroute , and it fixed the above issue , but then ingress controller was only able to sync the apis till 680 apis after that it failed with error -

ERROR provider apisix/provider.go:282 failed to sync {"error": "failed to sync 1 configs: GatewayProxy/hawkeye-ns/hke-int-apisix-ingress-controller-config"}

and apisixgateway throws error as - 192.168.24.247 - - [09/Jun/2026:11:55:37 +0000] 192.168.112.152:9180 "PUT /apisix/admin/configs HTTP/1.1" 500 58 0.066 "-" "axios/1.13.2" - - - "http://192.168.112.152:9180"

### Environment

apisix ingress controller cersion - 2.0.1
Adc version - 0.24.2
Apisix gateway version - 3.14

Standalone traditional mode without etcd

Start with status/updater.go:94 and apisix/provider.go:282, then inspect the GatewayProxy sync path associated with the reported /apisix/admin/configs failure. Reproduce with the stated standalone setup and larger route/config counts; done means identifying the cause of the sync limit or failure and documenting a verified resolution.

Written by the indexing model from the issue text.