feat: add LRU bucket metadata cache to presigned-url-plugin

[pyramation]

Summary

Adds an LRU cache for bucket metadata in the presigned-url-plugin. Previously, every requestUploadUrl call queried the buckets table even though bucket config (type, allowed_mime_types, max_file_size, etc.) is essentially static. Now the first request per databaseId:bucketKey pair hits the DB, and subsequent requests are served from cache.

Cache details:

• Composite key: bucket:${databaseId}:${bucketKey}
• Same TTL as the existing storage module cache (5min dev / 1hr prod)
• max: 500 entries (vs 50 for storage module cache, since there are many more buckets)
• clearStorageModuleCache() now clears both caches (coordinated eviction)
• clearBucketCache(databaseId?) added for targeted per-database eviction

Files changed:

• storage-module-cache.ts — new bucketCache LRU, getBucketConfig(), clearBucketCache()
• plugin.ts — requestUploadUrl now calls getBucketConfig() instead of inline SQL
• index.ts — exports getBucketConfig and clearBucketCache

Review & Testing Checklist for Human

• RLS bypass on cache hits: On cache miss the bucket query runs under the calling user's pgSettings (RLS-enforced). On cache hits, the cached result is returned to any user. Verify that all org members should always have identical bucket visibility (via AuthzEntityMembership) and that no bucket-level RLS restricts access to specific users within an org.
• Stale cache on bucket mutation: If a bucket's allowed_mime_types or max_file_size is updated, or a bucket is deleted, the cache will serve stale data for up to TTL (1hr prod). Confirm this is acceptable, or whether a cache-bust hook is needed on bucket DDL/DML.
• No test coverage: There are no unit or integration tests for the cache hit/miss behavior, TTL expiry, or clearBucketCache prefix-scan eviction. Consider whether tests should be added before merge.

Suggested manual test: Call requestUploadUrl twice with the same bucket key and verify the second call doesn't produce a Bucket cache miss debug log line.

Notes

• The bucketsQualifiedName interpolation in the SQL query is carried over from the previous inline query — not a new pattern.
• clearBucketCache iterates bucketCache.keys() while deleting; this is safe with lru-cache v10's iterator implementation, but worth being aware of.

Link to Devin session: https://app.devin.ai/sessions/4c882ba2dfbf4045adf85fb83cde6f77
Requested by: @pyramation

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 4 additional findings.