feat(watch-settings): add global vibration pattern override for notifications and calendar

[kchinnasamy]

Adds two vibration pattern pickers to Watch Settings — one for notifications, one for calendar reminders. Each shows the bundled DefaultVibePattern entries plus any user-created custom patterns, or "None" to fall back to the existing priority chain.

The selected name persists via LibPebble.updateConfig(). Notifications pick it up through BasicNotificationProcessor's existing priority chain (global override is the lowest priority, so per-app/per-contact rules still win). Calendar reminders use a new vibePattern parameter on CalendarEvent.toTimelinePin() / toTimelineReminder(), wired through PhoneCalendarSyncer.

Pattern labels are localized via R.string while the upstream displayName is preserved as the storage / VibePatternDao key.

Depends on matejdro/libpebble3#2; submodule ref repoints to origin/micropebble after that merges.

Test plan

• Notifications: pick a non-default, trigger a test notification, watch vibrates with the chosen pattern
• Calendar: pick a non-default, next reminder fires with the chosen pattern
• Switch back to None, defaults restored
• ./gradlew verifyPaparazziDebug clean
• ./gradlew :home:ui:runDebugDetekt :home:ui:lintRelease clean

[matejdro]

Now that matejdro/libpebble3#2 has been pulled, do we need to update the submodule ref to point to the new merge now? Or will it work regardless?

[kchinnasamy]

Now that matejdro/libpebble3#2 has been pulled, do we need to update the submodule ref to point to the new merge now? Or will it work regardless?

Functionally it works either way — 3b84f28b is now reachable from origin/micropebble after the merge of #2, so the build resolves the submodule fine. But you're right that the pin should track the upstream branch. do you want me to create a follow-up commit for that?

[matejdro]

I think it's fine. Thanks for your contribution!