[Bug]: Month to Date and Year to Date in Date Range Selector returns wrong range

[martonmesz]

Describe the bug

As per definition Month to Date should return a range from the first day of the month up until now, not including today.
Similarly for Year to Date, the range should go from the first day of the year up until now, not including today.
Instead it selects the end date as the last day of the month or year. This will return wrong data in case there is already some records for today (or the future for some reason, like predictions)

Steps to Reproduce

1. Create a date range selector as below:

<DateRange
    name=date_range
/>

2. Write a query that returns the selected values as strings

sql test
  select
    '${inputs.date_range.start}' as start,
    '${inputs.date_range.end}' as end

3. Examine the returned values

Logs

No response

System Info

System:
    OS: macOS 13.6.4
    CPU: (4) x64 Intel(R) Core(TM) i7-7660U CPU @ 2.50GHz
    Memory: 102.20 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.16.0 - /usr/local/bin/node
    npm: 10.8.1 - /usr/local/bin/npm
  Browsers:
    Chrome: 127.0.6533.120
    Safari: 17.3
  npmPackages:
    @evidence-dev/bigquery: ^2.0.7 => 2.0.7 
    @evidence-dev/core-components: ^4.7.2 => 4.7.2 
    @evidence-dev/csv: ^1.0.12 => 1.0.12 
    @evidence-dev/databricks: ^1.0.7 => 1.0.7 
    @evidence-dev/duckdb: ^1.0.11 => 1.0.11 
    @evidence-dev/evidence: ^39.1.1 => 39.1.1 
    @evidence-dev/motherduck: ^1.0.2 => 1.0.2 
    @evidence-dev/mssql: ^1.0.9 => 1.0.9 
    @evidence-dev/mysql: ^1.1.3 => 1.1.3 
    @evidence-dev/postgres: ^1.0.6 => 1.0.6 
    @evidence-dev/snowflake: ^1.1.0 => 1.1.0 
    @evidence-dev/sqlite: ^2.0.6 => 2.0.6 
    @evidence-dev/trino: ^1.0.7 => 1.0.7

Severity

annoyance

Additional Information, or Workarounds