fix: improve lifecycle log accuracy

[itslenny]

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

The lifecycle event logs used for usage tracking have accuracy issues:

• ObjectCreated:Put / ObjectCreated:Copy does not include old object size when overwriting an existing object
• Not logged if webhooks are disabled for the tenant causing usage tracking to be inaccurate
• Logs emitted in queue job which can cause duplicate entries if the job is retried

What is the new behavior?

• ObjectCreated:Put / ObjectCreated:Copy add an oldObject field with the replaced object's size. This lets usage be correctly attributed.
• Emit ObjectRemoved:Delete when a move operation causes an object deletion (e.g. restore version)
• All lifecycle events:
  • log once at dispatch time, before the event is queued. This prevents double counted usage.
  • emit lifecycle logs if webhooks are disabled

Lifecycle log change

This is an example of a lifecycle log diff after this change including oldObject if there is an object being overwritten

{
  "tenant": {
    "ref": "PROJECT_REF"
  },
  "name": "obj-name.txt",
  "version": "UUID",
  "bucketId": "bucket-name",
  "metadata": {
    "httpStatusCode": 200,
    "cacheControl": "no-cache",
    "eTag": "ETAG",
    "mimetype": "text/plain",
    "contentLength": 56,
    "lastModified": "TIMESTAMP",
    "size": 56
  },
  "reqId": "REQID",
  "uploadType": "standard",
+  "oldObject": {
+    "name": "obj-name.txt",
+    "bucketId": "bucket-name",
+    "version": "UUID",
+    "metadata": {
+      "eTag": "ETAG",
+      "size": 30,
+      "mimetype": "text/plain",
+      "cacheControl": "no-cache",
+      "lastModified": "TIMESTAMP",
+      "contentLength": 30,
+      "httpStatusCode": 200
+    },
    "reqId": "REQID"
  }
}

[claude]

Nothing blocking. The comments below are optional suggestions. There is no need to push a fix for them before merging.