docs: add information about contract size pubdata limitations (#1008)

docs/build/developer-reference/contract-deployment.md

@@ -52,6 +52,9 @@ Each zkEVM bytecode must adhere to the following format:
 - Its length in words (32-byte chunks) should be odd. In other words, `bytecodeLength % 64 == 32`.
 - It can not be longer than `2^16` 32-byte words, i.e. `2^21` bytes.
 
+Note: the `2^21` is a VM limit, but the deployed bytecode has to be published to L1, which imposes a pubdata limit, which is normally smaller.
+By default, for each batch, it's set to 100000 bytes for hyperchains using calldata DA, and 120000 per each EIP-4844 blob.
+
 The 32-byte hash of the bytecode of a zkSync contract is calculated in the following way:
 
 - The first 2 bytes denote the version of bytecode hash format and are currently equal to `[1,0]`.