chore(PULL_REQUEST_TEMPLATE): expandable sections

[fntyler]

🎟️ Tracking

null

📔 Objective

The "Reminders before review" and "Reviewer guidelines" takes up a large portion of browser/client real estate when creating, reviewing, or viewing PRs. This puts details into expandable sections.

Example:

Details

• Example 1 👋
• Example 2 👍

📸 Screenshots

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[github-actions]

🤖 Bitwarden Claude Code Review

Overall Assessment: APPROVE

This PR wraps the "Reminders before review" and "Reviewer guidelines" sections of .github/PULL_REQUEST_TEMPLATE.md in collapsible <details> blocks to reduce visual clutter when creating or reviewing PRs. The markdown is well-formed — blank lines are correctly placed around the <details> and </details> tags so the bullet list content inside still renders as markdown on GitHub. No code paths, dependencies, or security-sensitive areas are affected.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mimartin12]

I don't particularly like this, because for someone who isn't a regular contributor, they don't have the information front and center. I understand that it does eat a bit into overall screen real estate, but the information is helpful to how the team reviews PRs.