Reduce default value for frontend.visibilityArchivalQueryMaxPageSize

[tsurdilo]

Currently default value of dynamic config
frontend.visibilityArchivalQueryMaxPageSize
is 10000
This often is too large and leads to timeouts, in ui when listing archived and also cli
Users almost always reduce this to 1K which is same as default page size for vis operations.

Ask is to reduce visibilityArchivalQueryMaxPageSize to 1K

[yycptt]

This config only controls the max page size supported by the system. Each request can still specify its own page size to avoid timeout without tuning this dynamic config value.

The max page size is more for server side system protection. If the visibility archiver backend is some big data solution like Hadoop (we will support customized archiver implementation soon), reducing the max allowed page size and forcing more pages will add a lot of overhead.

If the concern is that max page size is used when pageSize is not specified, I think we should introduce a separate frontend.visibilityArchivalQueryDefaultPageSize instead.