chore: add daily workflow for testing deck configuration cases in edge (

#15295)

<!--
Thanks for taking the time to open a pull request! Please make sure
you've read the "Opening Pull Requests" section of our Contributing
Guide:


https://github.com/Opentrons/opentrons/blob/edge/CONTRIBUTING.md#opening-pull-requests

To ensure your code is reviewed quickly and thoroughly, please fill out
the sections below to the best of your ability!
-->

# Overview

Will close https://opentrons.atlassian.net/browse/RQA-2793
Adds github workflow to run hypothesis tests against edge daily at night

<!--
Use this section to describe your pull-request at a high level. If the
PR addresses any open issues, please tag the issues here.
-->

# Test Plan

Updated workflow, to test edge on `push:`
Will review to ensure workflow ran at specified time, 10:45pm

<!--
Use this section to describe the steps that you took to test your Pull
Request.
If you did not perform any testing provide justification why.

OT-3 Developers: You should default to testing on actual physical
hardware.
Once again, if you did not perform testing against hardware, justify
why.

Note: It can be helpful to write a test plan before doing development

Example Test Plan (HTTP API Change)

- Verified that new optional argument `dance-party` causes the robot to
flash its lights, move the pipettes,
then home.
- Verified that when you omit the `dance-party` option the robot homes
normally
- Added protocol that uses `dance-party` argument to G-Code Testing
Suite
- Ran protocol that did not use `dance-party` argument and everything
was successful
- Added unit tests to validate that changes to pydantic model are
correct

-->

# Changelog

<!--
List out the changes to the code in this PR. Please try your best to
categorize your changes and describe what has changed and why.

Example changelog:
- Fixed app crash when trying to calibrate an illegal pipette
- Added state to API to track pipette usage
- Updated API docs to mention only two pipettes are supported

IMPORTANT: MAKE SURE ANY BREAKING CHANGES ARE PROPERLY COMMUNICATED
-->

# Review requests
none
<!--
Describe any requests for your reviewers here.
-->

# Risk assessment

Low Risk, no changes to behavior

<!--
Carefully go over your pull request and look at the other parts of the
codebase it may affect. Look for the possibility, even if you think it's
small, that your change may affect some other part of the system - for
instance, changing return tip behavior in protocol may also change the
behavior of labware calibration.

Identify the other parts of the system your codebase may affect, so that
in addition to your own review and testing, other people who may not
have the system internalized as much as you can focus their attention
and testing there.
-->

.github/workflows/test-edge-with-hypothesis.yaml

@@ -0,0 +1,42 @@
+name: 'Testing Edge with Hypothesis'
+
+on:
+  schedule:
+  - cron: '45 22 * * 1-5'
+
+  workflow_dispatch:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.actor_id }}
+  cancel-in-progress: true
+
+defaults:
+  run:
+    shell: bash
+
+jobs:
+  lint-test:
+    name: 'edge testing'
+    timeout-minutes: 120
+    runs-on: 'ubuntu-latest'
+    steps:
+    - name: 'Checkout opentrons repo'
+      uses: 'actions/checkout@v3'
+      with:
+        ref: 'edge'
+        fetch-depth: 0
+
+    - name: 'Setup Python'
+      uses: 'actions/setup-python@v5'
+      with:
+        python-version: '3.10'
+        cache: 'pipenv'
+        cache-dependency-path: 'test-data-generation/Pipfile.lock'
+
+    - name: 'Install Python deps'
+      uses: './.github/actions/python/setup'
+      with:
+        project: 'test-data-generation'
+
+    - name: 'Run Hypothesis tests'
+      run: 'make -C test-data-generation test'