Fix/request date export

[aaronchongth]

What's new

Related to #689

• Adds Date column to minimal export
• Refactored task repository save_task_state
  • creating a new task state model explicitly setting request time, if it is a new task
  • updating all other fields when task already exists, leaving out request time and ID

To check exports, go to download button and select minimal export

To check if the request time stays the same, add these lines after here, outside of the else scope

        # debug
        debug_task_state = await DbTaskState.get_or_none(id_=task_state.booking.id)
        if debug_task_state is None:
            print('oh no something went wrong')
        else:
            print('request_time: {}'.format(debug_task_state.unix_millis_request_time))

Self-checks

• I have prototyped this new feature (if necessary) on Figma
• I'm familiar with and follow this Typescript guideline
• I added unit-tests for new components
• I tried testing edge cases
• I tested the behavior of the components that interact with the backend, with an e2e test

[codecov]

Codecov Report

Merging #690 (2a38ce1) into deploy/hammer (9b0d007) will increase coverage by 0.16%.
The diff coverage is 60.22%.

@@                Coverage Diff                @@
##           deploy/hammer     #690      +/-   ##
=================================================
+ Coverage          59.30%   59.47%   +0.16%     
=================================================
  Files                281      282       +1     
  Lines               5932     6003      +71     
  Branches             801      789      -12     
=================================================
+ Hits                3518     3570      +52     
- Misses              2260     2279      +19     
  Partials             154      154              

Flag	Coverage Δ
api-server	84.71% <94.64%> (+0.22%)	⬆️
dashboard	20.28% <0.00%> (-0.39%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...rver/api_server/models/tortoise_models/__init__.py	100.00% <ø> (ø)
...kages/dashboard/src/components/tasks/tasks-app.tsx	0.00% <0.00%> (ø)
packages/dashboard/src/components/tasks/utils.ts	0.00% <0.00%> (ø)
...ackages/react-components/lib/tasks/create-task.tsx	1.49% <ø> (+0.15%)	⬆️
...react-components/lib/tasks/task-table-datagrid.tsx	61.53% <ø> (ø)
...i-server/api_server/routes/tasks/favorite_tasks.py	91.42% <91.42%> (ø)
...api-server/api_server/models/rmf_api/task_state.py	100.00% <100.00%> (ø)
...-server/api_server/models/tortoise_models/tasks.py	100.00% <100.00%> (ø)
...ckages/api-server/api_server/repositories/tasks.py	95.06% <100.00%> (+0.46%)	⬆️
...ges/api-server/api_server/routes/tasks/__init__.py	100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[Angatupyry]

LGTM!
I think it was something we needed when we started adding those fields that should not be updated. So, thanks for these changes!
The only question I have is whether we should separate the update and create methods in different endpoints, but let's discuss that at our next meeting.