fix: limit max upload size

[vasco-santos]

Adds limit based on previous decisions, considering that S3 Put command has hard-limit of 5GiB.

• By limiting CAR size to 127*(1<<25), we guarantee max-4GiB-padded Filecoin pieces and have better utilization of Fil sector space.
• By receiving one more byte, we would immediatly get to 8GiB padded piece.

Closes storacha/w3up#827

[seed-deploy]

View stack outputs

• pr224-w3infra-CarparkStack

  Name	Value
  BucketName	carpark-pr224-0
  Region	us-east-2

• pr224-w3infra-RoundaboutStack

  Name	Value
  ApiEndpoint	https://pa34otg749.execute-api.us-east-2.amazonaws.com
  CustomDomain	https://pr224.roundabout.web3.storage

• pr224-w3infra-SatnavStack

  Name	Value
  BucketName	satnav-pr224-0
  Region	us-east-2

• pr224-w3infra-UploadApiStack

  Name	Value
  ApiEndpoint	https://cnwckji5l4.execute-api.us-east-2.amazonaws.com
  CustomDomain	https://pr224.up.web3.storage

• pr224-w3infra-BusStack

• pr224-w3infra-ReplicatorStack

• pr224-w3infra-UcanInvocationStack

• pr224-w3infra-UploadDbStack

[vasco-santos]

Also updated upload-api to enforce the limit right in the start

[Gozala]

Looks good to me. I do think however that it might be a good idea to pull in the data-segment lib and use it's functions to derive this number. That way future changes will propagate without us having to find all the places we have calculated the sizes.

[vasco-santos]

Looks good to me. I do think however that it might be a good idea to pull in the data-segment lib and use it's functions to derive this number. That way future changes will propagate without us having to find all the places we have calculated the sizes.

I would say this is implementation detail. Other users of data-segment can actually have other limits like 8Gb. I will merge but happy to iterate this further, even though I am not clear on what would mean using data-segment here. I guess starting from S3 limit of 5GB and find what is the bigger height that fit there. Afterwards, seeing what that size would map for a car size.