[INFRA] Add dev mode tests to schemacode workflow

[CodyCBakerPhD]

From discussion in #2129

Might take some fiddling around

[CodyCBakerPhD]

(starting from separate branch to verify failure on master before changing base to verify fix from other branch)

[CodyCBakerPhD]

How strange, the CI runs into no issue with regards to that install strategy - I will try again without the artifact package pre-step to verify my own sanity 😆

[CodyCBakerPhD]

Well, IDK what to say - all attempts to get the issue to show up in CI have failed...

If this isn't a general or reproducible problem (just a 'me' problem...) then I suppose I can just file away my own personal fix just for when I need to do this type of thing? WDYT

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.19%. Comparing base (daad867) to head (38c86db).
⚠️ Report is 231 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2130   +/-   ##
=======================================
  Coverage   82.19%   82.19%           
=======================================
  Files          17       17           
  Lines        1528     1528           
=======================================
  Hits         1256     1256           
  Misses        272      272           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[effigies]

Have you seen https://github.com/scivision/symlink-examples? Might be useful to debug your situation.

[CodyCBakerPhD]

Have you seen https://github.com/scivision/symlink-examples? Might be useful to debug your situation.

Have not, pretty useful - gave it a try

According to the script, symlinks are enabled and work great on my system (all tests pass) 🙃

But still not recognizing the file in #2129 during pip install -e on the git clone...

I'm thinking since this is tricky to test generally, we should close this failed PR attempt to enhance CI

And I leave it to you if you want #2129 or something analagous in your codebase, or feel free to close and I can remember to inject it on my own to solve my own difficulties