[#2280] Specify time periods for different repos in csv config

[CYX22222003]

Fix #2280

Proposed commit message

Specify time periods for different repos in csv config

This is to address the request to allow different periods for different
repos. 

Let's update the methods of parsing csv file and updating analysis
dates of repo configuration in the backend.

Other information

Sample CSV

Repository's Location,Branch,File formats,Ignore Glob List,Ignore standalone config,Ignore Commits List,Ignore Authors List,Shallow Cloning,Find Previous Authors,since,until
https://github.com/Golddirio/HacknRoll2025.git,main,,,,,,,,17/01/2025,19/01/2025

New format of summary.json

{
  "repoSenseVersion": "de62a593c5",
  "reportGeneratedTime": "周一, 10 2月 2025 21:53:52 SGT",
  "reportGenerationTime": " 16.18 second(s)",
  "zoneId": "Asia/Singapore",
  "reportTitle": "RepoSense Report",
  "repos": [
    {
      "location": {
        "location": "https://github.com/reposense/testrepo-Alpha.git",
        "repoName": "testrepo-Alpha",
        "organization": "reposense",
        "domainName": "github"
      },
      "branch": "master",
      "displayName": "reposense/testrepo-Alpha[master]",
      "outputFolderName": "reposense_testrepo-Alpha_master",
      "sinceDate": "2025-01-10",
      "untilDate": "2025-02-10"
    }
  ]
  ...
}

Related issue: #2283

[Airiinnn]

Thanks for the backend changes!

Left some minor nits regarding naming.

Also, I think tests for the changes in RepoConfiguration may be missing? Would be good to ascertain default values if hasUpdatedSinceDateInConfig and hasUpdatedUntilDateInConfig are false, and if the commits are filtered correctly according to the individual repo's date ranges.

Should update docs for the new fields too.

[Airiinnn]

Just thought of another thing, is sinceDate and untilDate in summary.json guaranteed to be the min and max of all the repos' sinceDate and untilDate?

[CYX22222003]

Just thought of another thing, is sinceDate and untilDate in summary.json guaranteed to be the min and max of all the repos' sinceDate and untilDate?

I will add additional steps to impose this constraint.

[Airiinnn]

Just thought of another thing, is sinceDate and untilDate in summary.json guaranteed to be the min and max of all the repos' sinceDate and untilDate?

I will add additional steps to impose this constraint.

Wait I was just asking if that is a constraint, not sure if it's supposed to be one.

I was mainly wondering what would be the intended behavior if --since & --until CLI flags are provided and are before and after the min and max of all repos' sinceDate and untilDate respectively. Is allowing this necessary for anything? Can't think of anything atm.

If allowed, will the commits in commits.json still only be limited to the individual repo's sinceDate and untilDate?

[CYX22222003]

Sorry for the oversight. I think the commit.json will still follow the individual repo's sinceDate and untilDate. But currently the frontend may not display in the correct way.

[Airiinnn]

Sorry for the oversight. I think the commit.json will still follow the individual repo's sinceDate and untilDate. But currently the frontend may not display in the correct way.

Alright gotcha, thanks! I'll make the frontend changes according to this then.

[Airiinnn]

I think you may need to update the UG docs (docs/ug/configFiles.md) as well.

But other than that, LGTM!