@jhb.software/payload-cloudinary-plugin@0.4.0

• fix: declare @payloadcms/plugin-cloud-storage as a peer dependency instead of a direct dependency, so it resolves to the same version as the host project's Payload suite and no longer pulls in a second copy of @payloadcms/ui (which broke the Payload admin with React context errors). Breaking: consuming projects must now install @payloadcms/plugin-cloud-storage alongside payload.
• fix: restore client uploads on Payload 3.82+. Client-uploaded documents now keep a usable url/cloudinaryPublicId, and files served from disablePayloadAccessControl collections no longer fail with "missing on the disk".
• fix: harden the client-upload signature endpoint (/cloudinary-generate-signature). The endpoint now only signs the timestamp, folder, and public_id parameters, only issues signatures for collections the plugin manages, enforces the configured upload folder, and rejects stale timestamps. The default access control now requires create access to the target upload collection instead of merely being authenticated.