Expose max-sync-message-size in options

[samutamm]

Fix #413

[codecov-commenter]

Codecov Report

Merging #419 (39d414a) into main (8ac2bab) will decrease coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #419      +/-   ##
==========================================
- Coverage   80.46%   80.43%   -0.03%     
==========================================
  Files          62       70       +8     
  Lines        7112     8093     +981     
==========================================
+ Hits         5723     6510     +787     
- Misses       1095     1223     +128     
- Partials      294      360      +66     

Impacted Files	Coverage Δ
pkg/cluster/cluster.go	50.68% <100.00%> (-0.94%)	⬇️
pkg/object/mqttproxy/storage.go	82.19% <0.00%> (-12.69%)	⬇️
pkg/object/mqttproxy/broker.go	75.00% <0.00%> (-4.69%)	⬇️
pkg/object/mqttproxy/client.go	78.60% <0.00%> (-2.50%)	⬇️
pkg/object/mqttproxy/session.go	82.20% <0.00%> (-0.11%)	⬇️
pkg/object/mqttproxy/spec.go	100.00% <0.00%> (ø)
pkg/util/ratelimiter/ratelimiter.go	100.00% <0.00%> (ø)
pkg/object/pipeline/mock.go	81.01% <0.00%> (ø)
pkg/object/pipeline/pipeline.go	88.65% <0.00%> (ø)
... and 10 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8ac2bab...39d414a. Read the comment docs.

[suchen-sci]

If user create yaml file larger than MaxCallSendMsgSize, I think we better log that to help them find problem. One way to do that is in statussynccontroller .go line 217, when err is not nil, except logging the error. We can also check if the length of kvs is exceed MaxCallSendMsgSize . Is this a good idea?