feat(billing): use allocated bytes in store/add receipt

[alanshaw]

Uses allocated property in the store/add receipt to count bytes added to the space. The allocated property will be 0 when the user tries to add a shard that is already present in the space.

❓ should we store a diff anyway? even though the size did not change?

refs storacha/w3up#1213

[seed-deploy]

View stack outputs

• pr303-w3infra-BillingDbStack

  Name	Value
  customerTableName	pr303-w3infra-customer
  spaceDiffTableName	pr303-w3infra-space-diff
  spaceSnapshotTableName	pr303-w3infra-space-snapshot
  usageTable	pr303-w3infra-usage

• pr303-w3infra-BillingStack

  Name	Value
  ApiEndpoint	https://cn5rqtwr16.execute-api.us-east-2.amazonaws.com
  billingCronHandlerURL	https://x755z2um66vnz2te35onrkzlku0zhufh.lambda-url.us-east-2.on.aws/
  CustomDomain	https://pr303.billing.web3.storage

• pr303-w3infra-CarparkStack

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

• pr303-w3infra-RoundaboutStack

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

• pr303-w3infra-SatnavStack

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

• pr303-w3infra-UploadApiStack

  Name	Value
  ApiEndpoint	https://5y20q5coee.execute-api.us-east-2.amazonaws.com
  CustomDomain	https://pr303.up.web3.storage

• pr303-w3infra-BusStack

• pr303-w3infra-FilecoinStack

• pr303-w3infra-ReplicatorStack

• pr303-w3infra-UcanFirehoseStack

• pr303-w3infra-UcanInvocationStack

• pr303-w3infra-UploadDbStack

[gobengo]

❓ should we store a diff anyway? even though the size did not change?

I can't think of a good reason to

[vasco-santos]

LGTM