fix: Remove LIST_LIMIT in workflow informer

[terrytangyuan]

Reverts part of the changes in #9691 since we need to verify correctness on pagination.

[jessesuen]

For posterity: the controller framework already uses a default limit of 500. And so previous change was unnecessarily reducing this. Also, based on log messages, I see the limit still being used 500 in some places, but my own custom value in other places, proving that the LIST_LIMIT was not working as intended:

EDIT: actually logs show it properly being used. I confused cronworkflow logs with workflow logs

$ LIST_LIMIT=10 LEADER_ELECTION_DISABLE=true go run ./cmd/workflow-controller/main.go -n argo --gloglevel 6 2> >(grep limit= | grep "workflows?")
I0927 18:13:47.423296   50187 round_trippers.go:553] GET https://host.docker.internal:51718/apis/argoproj.io/v1alpha1/workflows?labelSelector=%21workflows.argoproj.io%2Fcontroller-instanceid&limit=10&resourceVersion=0 200 OK in 11 milliseconds
I0927 18:13:47.431463   50187 round_trippers.go:553] GET https://host.docker.internal:51718/apis/argoproj.io/v1alpha1/workflows?allowWatchBookmarks=true&labelSelector=%21workflows.argoproj.io%2Fcontroller-instanceid&limit=10&resourceVersion=83227&timeoutSeconds=479&watch=true 200 OK in 2 milliseconds
I0927 18:13:47.534024   50187 round_trippers.go:553] GET https://host.docker.internal:51718/apis/argoproj.io/v1alpha1/cronworkflows?labelSelector=%21workflows.argoproj.io%2Fcontroller-instanceid&limit=500&resourceVersion=0 200 OK in 5 milliseconds
I0927 18:13:47.534087   50187 round_trippers.go:553] GET https://host.docker.internal:51718/apis/argoproj.io/v1alpha1/workflows?labelSelector=%21workflows.argoproj.io%2Fcontroller-instanceid%2Cworkflows.argoproj.io%2Fcron-workflow&limit=500&resourceVersion=0 200 OK in 5 milliseconds