DS-3293 Updated opening times in integration test case to a future da…

…te (#1038)

# Task Branch Pull Request

**<https://nhsd-jira.digital.nhs.uk/browse/DS-3293>**

## Description of Changes

Updating date to a future date for open timings integration test

## Type of change

- Integration test case scenario change for open timings

## Development Checklist

- [x] I have performed a self-review of my own code
- [x] Tests have added that prove my fix is effective or that my feature
works (Integration tests)
- [x] I have updated Dependabot to include my changes (if applicable)

## Code Reviewer Checklist

- [x] I can confirm the changes have been tested or approved by a tester

test/integration/features/F006_Opening_Times.feature

@@ -33,12 +33,12 @@ Feature: F006. Opening times
   @complete @opening_times
   Scenario: F006SXX6. Confirm recently added specified opening date can be removed from Dos
     Given a basic service is created
-    And the change event is "open" on date "Jan 01 2025"
+    And the change event is "open" on date "Jan 01 2026"
     When the Changed Event is sent for processing with "valid" api key
-    Then DoS is open on "Jan 01 2025"
+    Then DoS is open on "Jan 01 2026"
     Given the change event has no specified opening dates
     When the Changed Event is sent for processing with "valid" api key
-    Then there is no longer a specified opening on "Jan 01 2025"
+    Then there is no longer a specified opening on "Jan 01 2026"
     And the service history is updated with the "removed" specified opening times
 
   @complete @opening_times
@@ -55,29 +55,29 @@ Feature: F006. Opening times
   @complete @opening_times
   Scenario: F006SX8. Additional date changes open to closed
     Given an entry is created in the services table
-    And the service is "open" on date "Jan 01 2025"
+    And the service is "open" on date "Jan 01 2026"
     And the entry is committed to the services table
-    And the change event is "closed" on date "Jan 01 2025"
+    And the change event is "closed" on date "Jan 01 2026"
     When the Changed Event is sent for processing with "valid" api key
-    Then DoS is closed on "Jan 01 2025"
+    Then DoS is closed on "Jan 01 2026"
 
   @complete @opening_times
   Scenario: F006SX9. Additional date changes closed to open
     Given an entry is created in the services table
-    And the service is "closed" on date "Jan 01 2025"
+    And the service is "closed" on date "Jan 01 2026"
     And the entry is committed to the services table
-    And the change event is "open" on date "Jan 01 2025"
+    And the change event is "open" on date "Jan 01 2026"
     When the Changed Event is sent for processing with "valid" api key
-    Then DoS is open on "Jan 01 2025"
+    Then DoS is open on "Jan 01 2026"
 
   @complete @opening_times
   Scenario: F006SX10. Additional date changes times changed
     Given an entry is created in the services table
-    And the service is "open" on date "Jan 01 2025"
+    And the service is "open" on date "Jan 01 2026"
     And the entry is committed to the services table
-    And the change event specified opening is "open" from "10:00" to "16:00" on date "Jan 01 2025"
+    And the change event specified opening is "open" from "10:00" to "16:00" on date "Jan 01 2026"
     When the Changed Event is sent for processing with "valid" api key
-    Then DoS is open from "10:00" until "16:00" on "Jan 01 2025"
+    Then DoS is open from "10:00" until "16:00" on "Jan 01 2026"
     And the "service-sync" lambda does not show "report_key" with value "BLANK_STANDARD_OPENINGS"
 
   @complete @opening_times