Remove encoding message limit

[LucioFranco]

Users are seeing outofrange errors that I believe are originating from the server side so I removed the encoding limit, while we still have a decoding limit in place.

 Error: Failed to connect to database: `status: OutOfRange, message: "Error, message length too large: found 4225024 bytes, the limit is: 4194304 bytes", details: [], metadata: MetadataMap { headers: {"access-control-allow-credentials": "true", "access-control-expose-headers": "grpc-status,grpc-message,grpc-status-details-bin", "content-type": "application/grpc-web+proto", "date": "Fri, 06 Oct 2023 15:04:56 GMT", "fly-request-id": "01HC2RABMJX2SB2CHHMB8RZF0D-sea", "via": "2 fly.io, 1.1 fly.io", "content-length": "0", "server": "Fly/e440b950 (2023-09-20)", "vary": "origin", "vary": "access-control-request-method", "vary": "access-control-request-headers"} }`
 at Database.sync (/Users/me/Projects/app/node_modules/libsql/index.js:78:22)

[MarinPostma]

This issue will also be improved by #731