feat(cms): add partners collection

[sbcxty]

📝 Overview

What does this PR do? Briefly describe the changes and the goal of this PR.
Adds a new Partners collection to Payload CMS for the DurianPy website, per ticket #19. Includes schema (name, logo, websiteUrl), draft/versioning support with scheduled publish, role-based access control via checkCollectionAccess, and URL-format validation on websiteUrl.

🚀 Type of Change

• 🐛 Bug Fix: Fixed something that was broken.
• ✨ New Feature: Added new functionality or pages.
• 🗄️ CMS / Database: Updated collections, fields, or config in Payload CMS.
• 🧹 Chore / Clean up: Text updates, typos, or code cleanup.

---

🧱 CMS & Database Changes

Skip this section if no CMS or database changes were made.

• Migration Created: Ran payload migrate:create and saved the file.
• Local Verification: Verified changes in the local admin panel.

📊 Data Structure

Describe the new fields/tables or drag-and-drop a screenshot here:
fields:

• name (text, required)
• logo (upload, relation to media, required)
• websiteUrl (text, optional, validated as a proper URL format).

---

🧪 Testing & Validation

• Test Case Approval: Verified that test cases were commented on the assigned GitHub issue and approved by the Project Lead before development started.
• Unit Tests: Added or updated unit test scripts covering the new logic.
• Admin Panel: Verified behavior in the CMS Admin UI.
• API Check: Tested REST/GraphQL endpoints for correct data.

📸 Visual Evidence (Mandatory)

Important

Visual proof is required to demonstrate that the approved test cases from the issue were successfully met.
Please provide screenshots, screen recordings (GIFs/Videos), or sample API outputs proving that the feature satisfies all approved test cases and do not introduce regressions.

Schema and UI Verification

CMS Dashboard showing Partners under durianpy-website group

Schema shows correct input fields

Validation and Versioning

When all required fields are complete, the partner publishes successfully.

Attempting to publish with required fields left empty shows a validation error.

websiteUrl rejects invalid URL formats.

Scheduled a partner's publish date for a future time.

GraphQL query before triggering the job queue

Manually triggered the scheduled job via npx payload jobs:run

Re-ran the same query after the job ran

Access Control Verification

Group-level access (durianpy-website) grants full access to all collections under that group. Example: can create/read/update/delete on both Partners and Events collections.

Collection-specific access (Partners) can only access that collection. Example: can only create/read/update/delete on Partners but can only read Events.

Non-admin read access. Any authenticated user can read published and draft partners.

REST API Verification

Authenticated users can read draft and published partners.

Unauthenticated users cannot read draft partners.

Unauthenticated users can read published partners.

GraphQL Verification

Shows only published partners when querying with where: { _status: { equals: published } } filter.

Shows published and drafts when the query has draft: true flag.

Shows only published partners regardless of draft: true flag when user is unauthenticated.

--- ## 📋 Final Checklist

• Sync: Rebased from main and resolved conflicts.
• Pre-commit: Installed and ran pre-commit hooks successfully.
• Security: Verified no secrets or local credentials are included.
• Build: Project builds without errors.
• Visuals: Attached mandatory visual evidence proving all test cases passed.
• Migrations: Migration script included (if applicable).

---

🧠 Extra Notes / Questions

Add any additional context or questions for the reviewers here.
I didn’t strictly follow the read: anyone pattern because I noticed that it also allows unauthenticated users to read drafts. I used a helper function to modify the logic so only authenticated users can read everything. I used the same helper function for both Events and Partners collections. Would it make sense to make it a shared helper function, similar to anyone.ts, so it can be reused?

[jlorion]

Looking into integration I think we also need descriptions for partners

[ASPactores]

Kindly include a new field to store partner description. It should be an optional text.

[sbcxty]

Added the optional description field.