fix(attachments): use only qbit-object-storage's api package

Stop reading the bucket cap through StorageBucket.config() (the non-api
StorageBucketConfig, flagged by the qbit-bom guardrails, G1-arch).
Collaboration enforces its per-table cap; object storage still enforces
the bucket cap at put time. An api accessor is requested upstream.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

src/main/java/com/kingsrook/qbits/collaboration/attachments/AttachmentStorage.java

@@ -45,11 +45,14 @@ public class AttachmentStorage
    }
 
    /*******************************************************************************
-    ** Enforce the bucket's cap as well as collaboration's configured cap.
+    ** The bucket's own upload cap, when object storage exposes it through its api
+    ** package.  It does not yet (requested from qbit-object-storage), so this
+    ** returns Long.MAX_VALUE: collaboration enforces its configured per-table cap,
+    ** and object storage still enforces the bucket's cap when the object is put.
     *******************************************************************************/
    public long maxBytes(String name)
    {
-      return (bucket(name).config().getMaxUploadBytes());
+      return (Long.MAX_VALUE);
    }
 
    /*******************************************************************************