fix: add optional chaining to wakatime template to prevent rendering …

[endavis]

…errors

This adds null-safety to the wakatime template to prevent errors when the plugin is disabled or not configured.

Problem

When wakatime plugin is disabled (enabled: no in config), the template still tries to access plugins.wakatime.sections properties, causing:

TypeError: Cannot read properties of undefined (reading 'includes')

This happens because disabled plugins don't populate the data structure, leaving plugins.wakatime.sections as undefined.

Solution

Added optional chaining (?.) to all plugins.wakatime.sections accesses:

// Before:
if (plugins.wakatime.sections.includes(...))

// After:
if (plugins.wakatime.sections?.includes(...))

Changes across 4 locations in the template checking for different wakatime sections (languages, editors, os, projects).

Impact

• ✅ Template renders safely when wakatime plugin is disabled
• ✅ No breaking changes when plugin is enabled
• ✅ Prevents template rendering errors in generated SVGs
• ✅ Follows JavaScript best practices for null-safety

Testing

Tested with:

• Wakatime plugin enabled (works as before)
• Wakatime plugin disabled (no longer crashes)
• Wakatime plugin missing from config (no longer crashes)