Fix #2626: Fix Multi Year String Render For Single Day Events

[alvindera97]

Summary

Description

• Ensure single day events only render a single year string
• Include guarantees on condition for rendering end date year string for multi-day events.

Closes

• Bug: Duplicate Scheduled Year String Appearing For Single Day Events Whose Scheduled Year String Is Rendered #2626

Screenshots

Before

After

[GIgako19929]

This pull request enhances the event rendering logic by refining how event dates are displayed in the UI and adding comprehensive test coverage for these changes. The updates ensure that date-related information is only displayed when relevant, improving clarity for users.

Test Enhancements:

• Added two new test cases in events/tests/test_views.py to validate the correct rendering of event dates:
  • test_single_day_event_only_renders_event_date_year_string_if_relevant: Verifies that single-day events display the year only when appropriate, depending on whether they occur in the current or future year.
  • test_multi_day_event_only_render_end_year_information_when_dt_end_is_valid: Ensures multi-day events display the end year only when the dt_end field is valid, distinguishing between events spanning the current and future years.

Template Updates:

• Simplified the time_tag.html template to conditionally render the start and end year spans only when necessary:
  • Removed redundant start span logic for events scheduled to end in the current year.
  • Adjusted the placement of the end span to ensure it is displayed only when valid_dt_end is true, maintaining consistency with the new test cases.