Added sto4_start_time column to be initialized on unit creation

[rv0lt]

Read this before submitting the PR

1. Description / Summary

Now the column Sto4_Start_time will automatically be set in the Units table when the create-unit command is run. Instead of having to run the upgrade unit.

2. Jira task / GitHub issue

https://scilifelab.atlassian.net/jira/software/projects/DDS/boards/13?selectedIssue=DDS-1668

3. Type of change

What type of change(s) does the PR contain?

Check the relevant boxes below. For an explanation of the different sections, enter edit mode of this PR description template.

• New feature
  • Breaking: Why / How? Add info here.
  • Non-breaking
• Database change: Remember the to include a new migration version, or explain here why it's not needed.
• Bug fix
• Security Alert fix
• Documentation
• Workflow
• Tests only

4. Additional information

• Sprintlog
• Blocking PRs
  • Merged
• PR to master branch: _If checked, read the release instructions
  • I have followed steps 1-8.

5. Actions / Scans

Check the boxes when the specified checks have passed.

For information on what the different checks do and how to fix it if they're failing, enter edit mode of this description or go to the PR template.

• Black

• Prettier

• Yamllint

• Tests

• CodeQL

• Trivy

• Snyk

[codecov]

Codecov Report

Merging #1469 (ed04fab) into dev (d10dcf7) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##              dev    #1469   +/-   ##
=======================================
  Coverage   90.15%   90.15%           
=======================================
  Files          29       29           
  Lines        4407     4408    +1     
=======================================
+ Hits         3973     3974    +1     
  Misses        434      434           

Files Changed	Coverage Δ
dds_web/commands.py	80.27% <100.00%> (+0.03%)	⬆️

[i-oden]

Also we'll need to change the test dds_web/tests/test_commands.py::test_create_new_unit_success so that it checks that the sto4_start_time variable is set. In this case it would be good if you checked that only all sto4* variables were set and not sto2*.

[rv0lt]

@i-oden Should I also add checks for the rest of the parameters now that I am modiying this test. As right now only checks that the name was correct ?

[i-oden]

@i-oden Should I also add checks for the rest of the parameters now that I am modiying this test. As right now only checks that the name was correct ?

Yeah, you can do that, thanks

[i-oden]

Looks good!

[i-oden]

@rv0lt just rerun the tests, there's no actual error. We know about this bug since before, it does this sometimes