Triggering tests in stardis after every push to master branch

[KasukabeDefenceForce]

:pencil: Description

Type: :beetle: bugfix | :rocket: feature | :biohazard: breaking change | :vertical_traffic_light: testing | :memo: documentation | :roller_coaster: infrastructure

Triggering tests workflow in stardis after every push to the tardis master branch. This is related to #201 in stardis.

:pushpin: Resources

Examples, notebooks, and links to useful references.

:vertical_traffic_light: Testing

How did you test these changes?

• [ ] Testing pipeline
• [ ] Other method (describe)
• [ ] My changes can't be tested (explain why)

:ballot_box_with_check: Checklist

• [ ] I requested two reviewers for this pull request
• [ ] I updated the documentation according to my changes
• [ ] I built the documentation by applying the build_docs label

Note: If you are not allowed to perform any of these actions, ping (@) a contributor.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 36.57%. Comparing base (c107f27) to head (c11edf4). Report is 6 commits behind head on master.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #2708 +/- ## ========================================== + Coverage 36.47% 36.57% +0.10% ========================================== Files 183 184 +1 Lines 14664 14765 +101 ========================================== + Hits 5348 5401 +53 - Misses 9316 9364 +48 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.