Fix screen recording crash and Momentum tab preset logic

[eggmasonvalue]

This pull request addresses two main issues:

1. Crash on Screen Recording: Implemented onSurfaceDestroyed in both LifeCalendarService and DayCounterService to properly cancel scheduled tasks and stop the animation loop when the surface is destroyed (e.g., when screen recording starts). This prevents the app from attempting to draw to an invalid surface.
2. Momentum Tab Logic: Introduced a dayCounterMode preference to handle dynamic date calculations for "No Tomorrow" and "Vs Yesterday" presets. Previously, these presets saved static dates, causing the "breathing" indicator (current day) to become a static "past" item the next day. The new logic calculates start and event dates relative to LocalDate.now() daily, ensuring the intended visualization persists correctly.
3. Tests: Added unit tests for DayCounterModule to verify the dynamic date logic.
4. Build Config: Removed a hardcoded JDK path in gradle.properties that caused build failures in some environments.

---

PR created automatically by Jules for task 779938241268541767 started by @eggmasonvalue

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[eggmasonvalue]

Part of the request hasn't been complied with. So I'm going to restate:

1. Refactor the codebase to comply with best programming practices (a non exhaustive checklist: modularity, extensibility, single source of truth, linting, adequate comment density, separation of concerns, abstraction, encapsulation)

New:
2. Create a GitHub workflow that builds the apk and attached it as a release artifact on application of any tag that begins with "v".

[google-labs-jules]

Part of the request hasn't been complied with. So I'm going to restate:

1. Refactor the codebase to comply with best programming practices (a non exhaustive checklist: modularity, extensibility, single source of truth, linting, adequate comment density, separation of concerns, abstraction, encapsulation)

New:
2. Create a GitHub workflow that builds the apk and attached it as a release artifact on application of any tag that begins with "v".

I have refactored the codebase to address your feedback:

1. Refactoring for Best Practices:

   • Architecture: Implemented SettingsViewModel (MVVM) to handle business logic and state management for MainActivity, improving separation of concerns.
   • Modularity: Extracted Day Counter modes into a DayCounterMode constant object for better type safety and single source of truth.
   • Logic: Updated DayCounterModule to calculate dates dynamically based on DayCounterMode, fixing the "No Tomorrow" issue.
   • Linting/Style: Added KDoc comments to key classes and methods.

2. GitHub Workflow:

   • Created .github/workflows/android-release.yml which triggers on tags starting with "v".
   • The workflow builds the release APK using JDK 17 and uploads it as a release asset.
   • Updated app/build.gradle.kts to allow signing configuration via environment variables (Secrets), falling back to debug signing if secrets are missing.

[eggmasonvalue]

1. Add MIT License to the repo
2. Bug: Android's "material 3 expressive"/earlier "material you" concepts make the system theme adapt to the wallpaper's colour scheme. However this app doesn't seem to influence the system accent. Fix it.
3. Replace the square shape choice with a rhombus